Build better products with our product team
Add the ability to get a Fusion Test Drive account. There is already the ability to request a Workfront Test Drive account, so this would go hand-in-hand with that.
Description - - In Proof HQ, when creating Workflow templates it should allow us to add roles or teams that exist in Workfront.Why is this feature important - It reduces the need to maintain workflows in proof HQ and enhances the usage of proofing workflow templatesHow would you like the feature to work - When creating workflow templates in Proof HQ. While creating a stage and adding people to those stages, it should allow the user to not just select individual users but also allow them to select teams or roles from the respective Workfront instance.Current Behaviour - Proof HQ only allows the user to add individual users to stages when creating workflow templates in Proof HQ.
Objective of improvement:When two users share the same device and the Identity Graph Linking Rule is applied, let the anonymous browsing events associated with the same ECID be assigned to both profiles, rather than only the last one identified.Context:Applicant: The PL market, which seeks to implement specific use cases for SME.Example of use case:Offer leasing products or benefits by opening SME accounts to sme and/or individual profiles, if during anonymous browsing the user shows interest in SME products.Current situation:A user in Poland can have two profiles:Individual profile: customer_id=111, customer_type =ind (example).SME Profile: customer_id=222, customer_type=sme (example).Both profiles share the same ECID, as it is the same person using the same device.Current problem with Identity Graph Linking Rule:Public browsing events generated with the same ECID are assigned only to the last identified customer_id.This means that:If the public browsing event is the trigger, only the customer_id of the most recently logged in client will be impacted.Public browsing events are assigned exclusively to that customer_id at this point, which makes us lose the opportunity to contact the other profile.In order to impact both users, we need the ability to assign public browsing events to both profiles.
When using the 'updates' function or tab, it would be useful for our teams to be able to utilize this space in a fashion similar to email. IE- to add colored text to responses, in order to differentiate between users. Also, it would be helpful to allow certain updates to be 'pinned' to the top of the page so they don't get lost. OR to categorize them as "bulletins or job notes" of some kind to set them apart from the back and forth threads.
Description - Would love to be able to see user active statuses within Workfront to see who is active in WF, away or offline similar to Teams chat.Why is this feature important to you - This will allow us to see who we may need to follow up with outside of Workfront and/or escalate to another person on their team/manager.How would you like the feature to work - Colored circular icon next to each users name as it appears throughout the system - login, project owner, updates, task assignments, etc.Current Behaviour - N/A
Description - In the current single advanced proofing workflow, once a user is added to a stage, they can no longer be included in a later stage of the approval process. This creates the need to manually issue a second workflow if an individual user acts an an initial and a final approver. Some smaller teams I have worked with rely on one or two people to both do initial approvals and feedback while then also being the "final" approver, once all team member have given then comments and approvals.Why is this feature important to you -The need to manually create a new workflow for a "final" approval creates drag in the SLA's of certain proofing Workflows, or requires Fusion to act as a intelligent trigger to make the new workflow. For small marketing teams, Fusion is usually cost prohibitive.How would you like the feature to work - I would like an individual user to be able to be applied to each stage in an advanced proofing workflow. This will allow small teams in which managers act as both initial reviewer/approvers as well as a final last-mile approver to the overall workflow.Current Behaviour - Right now, once a user is entered as an user on any stage, they no longer appear in a user picklist when creating additional stages.
Description -Ability to filter DataFlow based on Target dataSet is missing in the AEP UI Why is this feature important to you -When there are 10s of more dataFlow going into a perticular dataSet, we only have an option to filter by source Application. Many times we want to see how many dataFlow are going into single dataSet. How would you like the feature to work -We want ability to filter dataFlow by target DataSet Current Behaviour -We can only filter dataFlow by source Application
Description - From one of my users, can we get the ability to delete a proof version in the "All Versions" page of a proof document? It makes more sense than having it only in the proof summary area, where you need to go through multiple clicks to get where you want. Why is this feature important to you - more efficient way to delete versions How would you like the feature to work - noted above, delete from the All versions location (picture 1)Current Behaviour - noted above, it shows in the proof summary location for version deletion (picture 2)
Design Studio is clunky and outdated in my opinion. Images and files are incredibly difficult to reorganize because I am unable to move more than on item at a time. Get an error message every time.Would love for a more seamless experience when navigating or making adjustments to existing folders.
Description:Our organization manages user permissions centrally through groups in Azure Active Directory (Azure AD). These groups are synchronized with Adobe Experience Cloud, allowing us to efficiently allocate product and profile permissions based on group membership. However, currently, administrative roles such as Product Administrator, Profile Administrator, Support Administrator, and System Administrator can only be assigned to individual users, not to groups. This creates a challenge for organizations that rely on group-based permission management and automation.Why is this feature important to you:Managing permissions at the group level ensures consistency, security, and scalability, especially in large organizations. Assigning admin roles to groups means that when a user is added to or removed from a group in Azure AD, their corresponding admin permissions in Adobe are automatically updated. This reduces manual intervention, minimizes human error, and helps maintain compliance with internal access management policies. Without this capability, we are forced to manually update admin roles for each user, which is inefficient and error-prone.How would you like the feature to work:We would like to be able to assign all administrative roles (Product Admin, Profile Admin, Support Admin, System Admin, etc.) to groups, not just individuals, within the Adobe Admin Console. When a user is added to or removed from a group in Azure AD, and that group is synced with Adobe, the user should automatically inherit or lose the corresponding admin rights based on their group membership. This approach should mirror how product/profile permissions are currently managed via groups.Current Behaviour:At present, administrative roles in Adobe Experience Cloud can only be assigned directly to individual users. Group-based assignment of these roles is not supported, which complicates permission management for organizations using directory group synchronization.
Does your organization run programs with multiple projects? Are your project managers responsible for managing large volumes of projects at the same time? Are you looking for an efficiency win? I think most organization will say yes and could really benefit from this idea. Idea: Implement the ability to quickly and easily assign users to roles at not only the project level, but also on the program level which would then cascade to all associated projects. Add a Workload Balancer at the Program level with ability to do Bulk Assignments relative to the cumulative roles identified in the associated projects. How could this work? Expose the Workload Balancer on a Program which would allow ability to assign/override any user on any given project for a selected role. If a Project Manager assigned a user at the Project Level, this would then subsequently override the Program Level assignment; there could even be an indicator carried up to the program level that indicates multiple users or the values as well for a quick display if desired. Current Experience Challenge: Project Managers must either manually assign users task by task, or potentially through bulk edit through sifting throught tasks, or by going to the Workload Balancer for every project. We commonly are running 10-15 projects or more and this requires a very significant amount of time every week to simply assign the same user.
We use the Workfront proofing tool to proof web pages that are created in AEM Sites. Ideally, we would use the URL function within the Workfront proofing tool, to generate the preview of the site and allow the reviewer to review and markup the proof. However, since only designers have AEM Sites access, the reviewer isn't able to view the proof when added as a URL to the proofing tool.Alternatively, the designer is uploading a pdf version of the web page as a document, to the proofing tool. But because it is not a text-based document, the reviewer does not have necessary proofing tools to mark-up text.Is there a way to leverage the URL function of the proofing tool, when reviewing AEM Sites pages prior to the page being published, even though reviewers don't have AEM Sites access? Or can the proofing tool identify text on these pdf versions of web pages (which would enable the text editing proofing options).
Right now i don't see any documentation on how you can create your own custom workflow activity. So people are going in and writing java script code to have that functionality implemented.It will be great to have some kind of documentation to follow on how to create the custom activity the right way and what should be the best practices to create any activity.
Request for Feature Enhancement (RFE) Summary: Multiple domain support for Manage Publication Preview Use-case: My customer APG would like to be able to preview the website in AEM that contains links to multiple domains. The Publication Preview functionality is not following the externalizer configuration to be used properly (screenshot of externalizer domains used below). Current/Experienced Behavior: It is possible to set multiple domains in the externalizer configuration, but only 1 domain is respected in the Publication Preview functionality, resulting in errors in the links when previewing the website (see 'part 2' screenshot below). The impact of multiple domains not being support in the Publication Preview functionality is that it is impossible for APG to properly preview their websites and use this feature properly to identify potential issues. Improved/Expected Behavior: An out of the box solution to support multiple domains for links in the Publication Preview would enable APG to preview their websites properly in AEM. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS feature release 2025.2.0, maintenance release 19823 Customer-name/Organization name: APG Groep N.V. Screenshot (if applicable): Code package (if applicable):
Description - Seed addresses used for internal testing in campaign) are currently included in Adobe analytics reports by default. It can skew engagement metrics.Why is this feature important to you - including seed data inflates KPIs and provides misleading view of actual engagement. Accurate reporting is critical for evaluating true campaign performance, optimizing segmentation and driving meaningful decisions.How would you like the feature to work - Automatically filtering them out from AA reports or giving an option to exclude seed addresses.Current Behaviour - Currently seed addresses are treated like real customers and no out-of-the-box method to filter them out which leads to inaccurate campaign campaign evaluation.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.