I have a suggestion which would like you to improve them to make Data Warehouse used more efficiently: Add "Delete or Cancel" function next to "Error" function in requests in Request Manager.At the moment, there is "Cancel" function in Scheduled requests only. Thank you.
Request for Feature Enhancement (RFE) Summary: Custom Tag predicates cannot be permanently configured to only pull specific namespaces Use-case: We want to have multiple tag fields not just one Current/Experienced Behavior: AEM has an out-of-the-box tag field. There are certain instances wherein stakeholders would like custom tag fields configured for certain tag groups. E.g. A tag field for “Content Type”, “Target Country(ies), “Campaign”. In the schema editor, there is no out-of-the-box way to limit what namespace is going to be displayed on a certain tag predicate. With that, even if there are multiple tag fields created, all of them will display the same set of tags or tag groups Improved/Expected Behavior: Have the ability to point tags fields to a specific namespace Environment Details (AEM version/service pack, any other specifics if applicable): AEMAaCS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: As a general user, I'd like to have a "recently used tags" feature that suggests tags in the textbox so that I don't have to remember what I previously used Use-case: A user is adding an asset and wants to add tags to it. Current/Experienced Behavior: User has to pick tags manually Improved/Expected Behavior: A list of tags that have been recently been added will appear and user will be able to select tags for the asset they are working on. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2021.7.5607.20210705T063041Z-210600 Customer-name/Organization name: Accenture Screenshot (if applicable): Code package (if applicable):
We currently call the privacy api deletion endpoint and then poll for status until we see the deletion has been completed. We have noticed during testing that analytics returns "status": "complete" and "message": "success" regardless of whether a customer existed in the system prior to the deletion request, which is a concern for our data governance team. Customer Care have advised that this is the current expected behaviour. Other products such as Target and Audience Manager, make this distinction by responding with status = complete but with the following additional detail:Audience Manager: "message": "Not applicable - Unable to resolve the user ids referenced in the request", "responseMsgCode": "PRVCY-6052-200", "responseMsgDetail": "Unknown user IDs are not applicable for this product."Target: "message": "Not applicable - user context not found" Are there any plans to introduce this depth of information to the analytics product response?
Right now, when an error or warning occurs on a Fusin scenario, everyone in the Fusion Team is notified. It would be extremely useful if we would select the role or team member to receive these notifications while suppressing them to all other roles/users. All team members don't need to see them so setting up the 'notification role' would be very useful. This is especially the case where a partner is hosting/maintaining a client's environment. Thanks.
Hello We have a lot of daily feedings created in Feeding Manager (Data Feeds) in Adobe Analytics. Because of last security audit we have been asked to make frequently changing a credentials for few hundreds of feedings. We have spoken with Adobe Customer Care and what we get informed, this cannot be done via API or any other tool which help us avoid manually changing secret key and access key. Changing manually lot of lot of feedings is a nonsense and a lot of time consuming. This is important so may i ask you for help and make implementation of that feature in Adobe Analytics ?Kind Regards Arek
We have several users who assign document approval tasks to individual approvers, approvers who often aren't familiar with Workfront. When those approvers are notified via email that a document requires their approval the notification link will take them to the task they are assigned, but when the document lives at the project level those approvers get lost trying to navigate WF and sometimes won't even have access to the higher level project itself.We propose finding a solution that allows approvers assigned to a task to have quick/easy access to project level documents (either through the initial notification itself, or via the task they are assigned) without giving them full access to the rest of the project, and without requiring a complicated click path.Current impact report on this Issue over the past year:23 Groups affected~3,000 users affected~16,000 projects affected266 hours annually of impact (approves clicking around lost, or seeking help/additional access as a result of this issue)
Currently, when you go to swap an image in a Marketo email and then select "design studio" you are seeing the images alphabetically and then have to search to find your asset. It would be great if the default view could be sorted by "last uploaded" date as well.
TL:DR - Ability to clone active Smart Campaigns.Currently we are going through the next phase of our Marketo integration. Phase one was set up as one Workspace, but as the business needs grew we have identified five additional Workspaces. We are now in the midst of establishing a new Master Workspace and building out the other additional Workspaces. Since launch of our initial phase we have establish complex business logic that runs many of our triggered and scheduled campaigns. Rebuilding these campaigns as inactive shells in the new master, pausing the old and reactivating the new will be extremely painful and time consuming. IDEA: Being able to clone an active Smart Campaign to another Workspace, and once cloned to the new Workspace all of the triggers are deactivated, essentially leaving it a clone waiting to be modified or reactivated would be extremely helpful and a time saver. I'm sure there are large complicated businesses that have run into this issue as well as their needs evolved.
In an EMAIL notification that a user has an issue or project approval, they're able to see Priority in the notification without clicking into the details. This is helpful especially for high or urgent approvals. However in the respective TEAMS CHAT notification, no priority shows. The Chat is even better for this notification bc if it's high/urgent, they'll be able to quickly see that in the ping (and ppl tend to pay more attention to pings than emails). Want priority to show in the Teams chat notifications, or even just for high/urgent priority approvals.
Make it possible to set the default Action Timeout in the property settings
The Fusion log history is lacking as an "enterprise" grade application. The information on who made a change to a flow and when it was made is available. However, there is no information on what change was made. Not having this information makes the log pretty useless.
We ran into the problem, that somehow the notification settings of our audit user have been changed. Only two people have access to that account and both denied doing the changes themselves. So it would have been great to see by whom those changes were made.
Id like to be able to cross reference more than one field when you send an alert or create a task. Ex: If x and y = true -> then send alert. instead of if y = true or y = true -> send alert
Request for Feature Enhancement (RFE) Summary: Add (optional) approval step (or something similar) before deploying to a Dev or Stage environment Use-case: The environments are used by a different company to test the software and therefore requires alignment of the deployment maintenance. As the build time could vary a lot, this maintenance window needs to be quite large. (With this option the 15 minutes of the deployment step + 10 minutes smoke test as maintenance window would already be sufficient as the pipeline and its long running build and unit testing steps could be started much earlier.) Current/Experienced Behavior: After "Code Scanning" step the pipeline will immediately start deploying the new software package. Improved/Expected Behavior: Option to pause the pipeline before executing the deployment step. This option should be available for non-production as well as production pipelines. Environment Details (AEM version/service pack, any other specifics if applicable): not applicable Customer-name/Organization name: Volkswagen Screenshot (if applicable): Code package (if applicable):
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.