Hi @jantzen_b , given that Idea of v2.0 processing rules API is still a very current and requested feature, it doesn't seem appropriate to archive yet. Perhaps once the feature has been added?

Hi @tomo_xxx , you should be able to access it from there. Even if you have a single use of the Analytics extension it will load the library. So in a core, "Page Bottom" rule, run an Analytics, "Clear Variable" action. In your console, set _satellite.debugger(true) to view the logs within Launch to ...

@Joshua_Eisikovi , just checking, but did you actually check with the System Admins before granting access?

Ultimately, it is a bug in Search Discovery's extension. You may want to reach out to them. Chances are you are using an escape character in your product string and their extension isn't catching them.

Hi @Luca_Lattarini , this looks like an error in some custom code (or erroneous extension).In particular it looks like someone is referencing a promise that has never declared (e.g. promiseEG.then(()=>...., by default promiseEG would be treated as a null object if not declared properly and the inter...

A lot of the issues you mention (e.g. slowness) are likely due to outdated API built around the processing rules CRUD. It may be worth supporting the requests for updating the API on the ticket, here, which would also enable easy fixes in the UI.

Hi @Brian_Kent_Watson , you mentioned that "API support is not available in API 1.4..."It is available it's just not very useful and requires inconvenient text parsing. Outside groups have had to compensate for this poorly written API.

Hi @prathap08 ,If you are setting it into prop2 with document.location.href you can use the following javascript to set the variable:s.prop2 = document.location.href.replace(/([^:])\/\/+/g,"$1/"); This will replace every instance of repeated "/" unless directly following a ":". Note: If you are use ...

Additionally, @Luca_Lattarini , you may also want to exclude the permissions that are company-wide. Even though it is less convenient for the vendors since the ability to Manage Properties means they cannot create their own properties, they also won't be able to reconfigure/delete them.

Hi @tomo_xxx ,You may want to check several things before looking for the AppMeasurement.js file.1. Make sure that the implementation code is being hosted on Akamai because otherwise it may be coming from a different source altogether. You could start just by checking that there is a assets.adobedtm...