Adobe Experience Platform

This should either be renamed or give the user greater control over what gets cleared.  From my understanding in talking with Support, the Clear Variables (previously clearvars()) only clears props and events, but not evars, so I thought it was odd that something that is labeled "Clear Variables" would only clear certain variables, but not others (especially not the one with "var" in it's name).

The archives created for manual deployments contain redundant folders (redundant in a self-hosting environment where you already know where you want to host the file and usually have a specific folder for it), and creates chaos for people using deployment tools or a CMS for publishing (regardless of which CMS it is). Our ops team are going to very quickly hate me because of the large amount of work this is creating for them every time we do a release.We need the ability to set an option so that archive files do not have folders for the Company or Property, and ideally do not have a folder for the Build. Whilst undesirable, it would be much easier for us to live with only Extension folders and not all the other superfluous folders.In a perfect world, we could create just a flat archive, which does not contain any folders, and we are responsible for ensuring it is in its own folder.

I liked editing rules in DTM. The Rule Type was always clear (event, page load, direct call) and the Rule Name stayed on the page when editing the rule. I can't get used to the multi-screen experience where clicking to edit any of the configuration navigates to another view and the rule name is gone. Very difficult to keep track of where you are when only partial information is displayed. Please update this asap.

It would be nice to have a possibility to tag rules and data elements, like you can tag post here in the forum. With this it is much easier to search for rules and data elements, especially if you have more then a few of them .

Sometimes, like when transitioning to a new report suite, you need to send Analytics calls to different report suites utilizing different variable mappings.  In DTM you could do this by installing 2 instances of the Adobe Analytics tool in your property and naming the trackers differently.  This cannot be done in Launch.We would like to see the Analytics extension updated to allow multiple instances of the tracker.  Basically, make the s_gi() capability available in Launch without resorting to a lot of custom code.For implementation ideas, look at the Google gtag Extension that Acronym published.

If I have different libraries I would like to be able to edit the revisions of rules, data elements etc. in all libraries. Unfortunately only the latest revision can be edited. And the latest revision is always the same that is edited though the interface.Two options would be could:"Set as latest revision" from the library interfaceSwitching the Working Library shows the Revisions of the library in the interfaceWhen editing e.g. a rule again saving would create a new latest revision.

It would be nice to visually see the publishers name or email next to the build date in the activity log or have the ability to see it when the user hovers over the succeeded/fail build message. It would be helpful to have a search bar within the Audit Events tab that filters by the title columns.

Our Launch Properties are used across multiple domains. In the AAM UUID Cookie configuration in the AA extension we need to be able to set the UUID Cookie Domain to be variable depending on the hostname of the page which is being viewed. Unlike most configuration values in the extension, this one does not allow the use of a Data Element and so we're not able to achieve this.

Support the logic of parent/child properties to be able to share a standardized set of rules/elements/.. down to child properties. Child properties would only add/overwrite a sub-set of rules/elements.

Events need the same type of set/no-set logic based on the value that is available to sprops and evars within the "Set Variables" action block.With variables, as it works today, if eVar2 is set to a data element that returns an empty string - it will not set the variable or send the info within the record call (default functionality, that is also optional - great stuff! ).With events, it doesn't seem like we have this choice.  We should be able to set the value of an event to a data element that can return something like 'False' or an 'empty string' , controlling whether or not the event really gets set with the record.

When I click into a data element, is it possible to get a list of all rules or other data elements that reference it?This way, I can ensure there is no duplicated effort of data elements and the number of data elements are not more than once. This also helps to get rid of data elements that are not used any more.

I would like to have the same DTM notification email system in Launch. It was useful to keep key stakeholders across changes.Thanks,Lucia (Stuff Limited NZ)

Please increase the width of the name field on the create/edit rule view to 100 percent.

Rule event, condition, and action names are automatically set based on the extension and event/condition/action type—great! It would be helpful to be able to append text to that name from the type's view. For example, when creating a direct call event with identifier "foo", the extension could pass "foo" up and Launch would use it to automatically set the name to "Core - Direct Call - foo" instead of just "Core - Direct Call".To be clear, this idea is limited to adding the framework to easily allow this in extensions and does not include updating all Adobe extensions to use it.

Hello, It is at the moment quite cumbersome to look and compare revision within Launch. I feel that the problem lies in the following element : - Revisions are all numbered and starting some time, you are never sure which one is the live one. - Some revisions version exists but where never published liveThe idea(s) would be to have an information next to the revision version in order to identify: - The version that is live- The version which is in a Library (should be the highest number but not always)So you can easily compare : - Version X vs Live version- Version in a Library vs Live Version Also, it would be great to clean the version / revision that were never set live at any point. When a revision is build live, look at all the previous revision and delete all the one that were between 2 live versions. It would help clean the versioning.

It would be great to create like a MASTER Property (like a library) where rules and extensions can be committed to other properties. So the Properties can easily inherit the rules and extensions from the MASTER. If a new property is created you can then link it to the master and it gets all the data-elements, rules and and and. Would be extremely  helpful, otherwise we have to create each Pageload rule again and again. I know it is possible to copy rules from property to property but an automatically inherit would be so valuable.

it would be nice if there is a way to fetch information about installed extensions. what I think of is having some data available (by default) about every extension installed.basically, I would love to have access to the following information about each extension:- name (friendly name)- id (or some other unique identifier)- version- publish datehaving this information could be used in several ways:a) write information in a custom prop for reportingb) use reporting information for better reporting/segmenting datac) add checks if single extensions or combinations of extensions are installed and throw errors in dev/staging (quality check while developing)d) run certain code only if a specific extension is installed and has a defined version number

StringEncoder.java class in com.adobe.marketing.mobile:sdk-core library supports only SHA-1 and our company requires to have at least SHA-2 for encoding.Thanks

Something that was a potential security concern in DTM is become a breaking defect in Launch. If I have a page that doesn't load on the typical "http" or "https" protocol, I would need to specify a protocol in my embed code, so this:<script src="//assets.adobedtm.com/9310dd7d04eb33be499693ff5cc9558ffcacdf54/satelliteLib-38d69d073d347 9a9c730481247813276cb9fc3c0-staging.js"></script>Would become this:<script src="https://assets.adobedtm.com/9310dd7d04eb33be499693ff5cc9558ffcacdf54/satelliteLib-38d69d07 3d3479a9c730481247813276cb9fc3c0-staging.js"></script>In DTM there is a potential security flaw with this, where it will load my main file as HTTPS, but any of the other files (like my appMeasurement library) get loaded as HTTP. (You can see this on Testing Launch Utility if you load the page as "http" or download it and run it locally- the main library is secure, but the appMeasurement and mbox files are non-secure ):In Launch when a file is run locally (or throug

We have introduced an issue with the latest release and I know exactly which rule is responsible. Now I want to check what was changed when, but with the audit log it is nearly impossible to find the changes. So I suggest a filter mechanism for all the headers:date (range for the filter)propertyuseretc.

Similar to a feature requested here Ability to Turn Off/On ActivityMap Module in Adobe Analytics Extension, it would be great to see the ability to add/configure analytics plugins while having the "Manage library for me" option selected. Right now this still needs to be done within the custom library code section.I realize this is an extension feature request, not directly related to the launch platform. Is there a way to make requests for individual extensions outside of this forum?

Current DTM includes icons over the rule lists that indicate Adobe variables, Google Analytics, Google Universal and Additional Tags.  This would be a welcome addition to Launch, especially for when the rule lists get long.

When editing a Rule, the user cannot see which rule is currently being edited! Very annoying, as you always need to step out of the configuration to make sure you're not working on the "wrong" rule...

In current versions of the SDK (v4 and AEP), trackAction events do not include the name of the Screen or State the action occurred on - by default the pageName parameter is populated by the App Version, and this appears to be discarded on processing.Because of this, there is no out-of-the-box way to report on Action Name (or other dimensions set on a trackAction) against the Screen/Page/State that the action occurred on - a very common, straightforward report. This forces implementations into bulky workarounds such as including Page Names in the Action Names or creating a second Page Name custom dimension.If trackActions captured the actual Page Name, this would make a very common scenario much easier to implement & report on.

In DTM the delay link activation breaks the JS-based links and in some instances anchor links functionality.The request is to either:1. Have an option to disable the delay link activation on links that are pure anchors, contain the URL of the existing page + an anchor, or contain javascript commands.2. Revise the functionality of delay activation so that the delay just delays the activation of the link, not stops it and then takes user to that URL.Including a sample code that successfully can achive both of these requests:/**  * The functions executes for x milliseconds.  * @param  {Integer} ms  Number of milliseconds the function should run.  * @return  */ export default function waitMilliseconds(ms) {   var start = new Date().getTime();   var end = start;   while(end < start + ms) {     end = new Date().getTime();   } } /**  * Delays the links from moving forward on click by 1 second  * to allow the data to go into analytics successfully without the delays.  */ export default func