Build better products with our product team
Adobe informed us that group replication for Workfront is not currently available. Overall Workfront access can be provided via Admin Console, however specific Workfront level user groups/access levels/teams cannot be managed via Admin Console. Access Levels, Groups, and Teams must be managed directly in Workfront. Ideally, Group Replication for Workfront would be supported as this would allow Admin Console to be used to manage more detailed access levels for Workfront rather than just overall access. This would prevent having to use both Admin Console and Workfront to manage user permissions. Related article discussing this topic:
Request for Feature Enhancement (RFE) Summary: Currently in AEM DAM AVIF file are not supported. It would be required to support this format whenever user upload the image and want to use it in the content Use-case: When Author upload AVIF file (file with AVIF extension, file in AVIF format) to DAM THEN file is processed correctly, thumbnails are generated AND Author can use file in AVIF format on a page (eg. in the Image component) Current/Experienced Behavior: Author can't use file in AVIF format on a page (eg. in the Image component) Improved/Expected Behavior: Author can use file in AVIF format on a page (eg. in the Image component) Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: AEM sites Rollout and publication issue Use-case: When a editor rollout and publishes a master page, the publication process start publishing the live copies in random order and fails when it encounters any market page that is locked to a user. This results in inconsistencies leaving the page changes published to few random markets. Ideally this should have completely stopped or skip the locked page, deploy to rest and notify about skipped page. Current/Experienced Behavior: The rollout/publication does not follow a predictable sequence and succeed for markets until it encounters locked pages then silently fails making it difficult to track progress There is no summary or report indicating which locales were successfully published and which were skipped. This results in inconsistent rollout and makes it hard to identify which pages need manual intervention Improved Before initiating rollout publication, the system should check for any live copy pages that are currently locked by users If any locked pages are detected, halt the entire replication process. Display a clear error message indicating which pages are locked and by whom. Environment Details (AEM version/service pack, any other specifics if applicable): AEM version - 6.5AEM service pack - 6.5.22 Customer-name/Organization name: British Airways(BA) Screenshot (if applicable): Code package (if applicable):
When working with offers we cant filter the offers on the "created by" filter. It is not an option in the filtering menu and its not an option in the canvas/offers list. You can get the data to show in the offers list, but you cant click on that column to filter/sort on that data, like you can with "last modified" and "modified by". For our users it could be hard to find the offers you have created when we have over 40 creators of offers in our platform. Therefor there is a need and wish for a better filtering and listing of offers based on "created by" data.
Create the ability to assign a default view on a portfolio and program level. We extensively use custom form data. Projects in different portfolios and programs will often have specific custom forms tailored to that project type. It would be very useful not to have to change views when navigating through different portfolios.
DescriptionDynamic text visualization would allow the inclusion of dynamic fields (dimensions, metrics, segments, or date ranges) directly within text elements. This enables text to automatically update based on the context of the analysis, making dashboards and reports more interactive and informative. Why is this feature important to youProvides greater flexibility in storytelling with data.Reduces manual effort of updating static text when filters or date ranges change.Enhances clarity by showing contextual information.Improves user experience by making text responsive to analysis changes. How would you like the feature to workText visualization should support placeholders that can be linked to dimensions, metrics, or filters.When a user changes a filter (e.g., date range), the metrics displayed should automatically refresh to reflect the new values.Ideally, users can select fields from a menu or insert them via a formula-like syntax.Example: {{ date.range }} there were {{ orders.sum }} {{ orders.dimension }} from {{ country }} -> this would result into: Last week there were 567 orders from USA. Current BehaviourText elements are static and do not adapt to changes in filters, segments, or date ranges.Users must manually edit text to reflect updated analysis context.This limits the ability to create dynamic, self-explanatory dashboards.
We shouldn't have to have our browser's zoom set to 100% in order for WF to display reports/lists properly without auto scrolling upward on its own.We didn't used to have to do this, but about a week ago something changed.I've already worked with support who said something changed and now it has to be at 100% zoom or when you scroll down to the bottom of a report, it automatically and on its own starts scrolling upward making it difficult to review the data.
Description - Calculate work effort based on planned hours on task instead of workday.Why is this feature important to you - It's a more realistic situation to calculate work effort based on the planned hours of the task rather than the workday. How would you like the feature to work -We would like our users to be able to change the work effort on their task based on the original planned hours of the task, not the workday. Current Behaviour - Work effort is calculated using 8hr workday.
Description -I would like to more easily keep track on day-to-day changes in number of qualified profiles for batch audiences. Why is this feature important to you -AJO end users often change audience criteria and want to follow-up on the effect of that change when it comes to difference in audience size. How would you like the feature to work -I would like the audience properties to show number of qualified profiles from both the most recent batch update as well as the previous one. Current Behaviour -Currently AJO end users have to keep documentation somewhere else than AJO to keep track on the difference in audience size after a change in the audience criteria.
Description:Having he ability to remove/delete/replace custom dimensions from those 10 in the system tab.
When you work in the Journey builder creating a new Journey, or want to do changes in an older one, the change you find necessary to do often is actually in an Audience used in the Journey. In other cases you need to check an Audience you have used. Today you need to go out of the Journey builder and find the wanted Audience in the Audience overview. In the Journey builder interface where you select Audiences to use, it would have been nice it you actually could go directly to the Audience and open it from this page/view. It is a little misleading that you have a edit button there, but the only ting that happens is that you open a popup with the total number of Audiences you can select from. You dont find the one that is selected directly and you cant open it to edit on it. That would be a way more helpful feature - open and edit the already selected Audience, directly from the Journey builder interface.
We have experienced that expressions with audience names in the expression is not updating if the audience is changing name. This causes the expression to fail. since the audience "is no longer there". This causes problems for the users of the platform and the customers receiving communication. In bigger organizations like ours there are many different teams working in AJO at the same time, also in different countries. If there is an audience library to be used of many users, as part of staying under the audience threshold limitation, many user can use the same audience for different kind of activities. Both as inclusions, as well as exclusions in the organizations activities. And many will therefor also have the same audiences used in expressions. We see that this now causes big and surveil danger in using expressions in AJO Journeys. An audience name can easy be changed, planned or by mistake. And the consequences can be big when expressions then stop to work as planned, only because of a name change. The changer of the name might not even be ware of all the Journeys where this audience name is been used. Backtracking this can be a though and hard job, finding all the logical breaks that now has has come. We suggest that there is "another" connector in the expression builder that uses the ID for the audience rather than the name. Relaying on a name is not a good idea in general. You can showing the name in the creator, but in the back is should really be an ID that is used, something stable and reliable that doesn't change regardless of name and content of the audience. This discovered weakness can cause surveil damage to our customers, without anyone knowing.
In AJO we have this advanced content locker when we work with email templates. But we experience an weakness in how we can work with this. And that is when our email templates is created by fragments. You can lock and basically control most of the content in a pre defined template. But that is only when all needed fragments in already in the template. When users -witch is common usage, drag and drop new fragments they want and need into the template, from the fragments library/menu, there is no content locking on those. It the fragment you drag into the template has text or other content areas that should not be changed, or the formatting should be locked it would be nice if this could be defined on the fragments itself. No we cant set any limitations when it comes to content in a fragment, when is comes to locking fragment content form been edited after been dropped into an email template.
Description - possibility of saving tags or attributes for each node in a journeyWhy is this feature important to you - for better analysis in CJAHow would you like the feature to work - choosing characteristics when creating or changing a journey campaign in AJOCurrent Behaviour - it is only possible to aply tags to the whole journey, not to a specific node.
In bigger organizations with many users that uses AJO if can be difficult to make all use a common naming convention to structure the content created in AJO, like audiences, Journeys and offers. Even if we have the folder possibilities it is a good thing to have a good naming convention when searching or navigating trough the content. Even all know and understand this importance, it is hard to make all users follow this in there hectic daily work. The idea is to have the possibility to create a set of PreFixes of names that you as a user can use when creating content. F ex you just select the name of the PreFix by selecting it with a checkbox or from a dropdown, when creating things. When saving the PreFix will then be saved as the first part of the name of the thing you create. If you have operations in different countries you might want to have a country PreFix, in addition to f ex the department you work in. A set of naming PreFixes could then be f ex.No_SalesSE_SalesDK_SalesNO_SupportSE_SupportDK_SupportWhen creating audiences, Journeys or offers you select on of this PreFixes that will be part of the final name. As a user you can f ex name your audience "missed incoming calls oct 2025". The final name in AJO will, with the PreFix be: "NO_Support - missed incoming calls oct 2025" Now all users can from the name see and understand that this audience is not just about missed calls, but it is in Norway and it is missed support calls. This can off course be solved manually by having this as routines for all users. But as we all know it is hard to get all to follow routines like this, especially when resources coming and going over time. Therefor it would be a great feature to be able to administrate something like that from the tool itself.
We are facing a issue where many of the stakeholders that is doing proofing of emails is not an AJO user, and can therefor not use the build in features for this. The workaround is hard and time consuming, like taking screenshots and distribute those around in the organization or creating a own Journey with test users for every time you have a change in the email contain. In most cases this means creating several journeys and sending tests as a real send out to stakeholder many times before the final email goes live.We are therefor wondering if the "mirror page link" could be used instead. if that could be distributed before the mail is rendered and sent out. This means that when we create a proof in AJO, it would be nice if the "mirror page" link also could be generated and be public so that this link could be distributed to Stakeholders that is not AJO users. Be able to share a final version of an email through a public link before a final send out has been rendered would be very helpful when it comes to creating a faster and better workflow - for many organizations we think.
Description - Ability to copy and alter requests in new unified experienceWhy is this feature important to you - Team members utilize this functionality when submitting similar requests with minimal changes. Efficiency for team members.How would you like the feature to work - Ability to copy requests and make edits in new unified experience similar to legacy experience.Current Behaviour - Functionality not available in new experience. Users have to toggle back to legacy to create copies.
In a global company, the Adobe team recommends consolidating multiple countries in a single AEP Organization, with separate sandboxes. However, Adobe Target doesn't have the same hierarchy of "organization + sandboxes", so the Out of the box integrations are not available:* The Adobe SDK don't allow two deployments across digital channels, one for AEP Org and another for Adobe Target Org. Therefore, we have to manage a dependency by uninstalling the Target SDK and modifying the integration through the Server Side, which is not friendly for marketers.* Audience destination nether works. We have to share segments through Tag Manager or create a custom microservice to integrate Adobe CDP + Target. Some suggestions:* Allow the installation of two SDK, one per Organization, across digital channels* Align the Adobe Target and AEP hierarchies (Org + Sandbox)* Create a OOTB destination with Target in a different Org to avoid creating an in-house microservice
Why is this feature important to you - It would be very useful to see how many times a dashboard has been opened/used, by whom it was opened/used statisticsHow would you like the feature to work -We request the development of a user-friendly Workspace Usage Report interface within Adobe Analytics that allows admins to easily view and analyze dashboard usage metrics without needing to extract or parse raw logs.Current Behaviour - At present, dashboard usage can only be reviewed by accessing Usage Logs, which is not practical or user-friendly for administrators or business users who need to understand how dashboards are being accessed and utilized.
Description: An email alert is generated when a new proof version is created, but not for a new document version. This functionality is important. Why this feature is important: Users who do not select proofs, such as agencies updating an asset based on feedback from the V1 Proof, should be able to upload a new version of an existing proof as a document. This action should notify the Project Owner/Team (based on their settings) that a new document version has been added. Desired functionality: When a new document version is added, the system should notify the Project Owner/Team (based on their settings) of this update. Current behavior: When a user adds a new version as a document, no email alert is sent. Users must either share the document directly with their point of contact or use an @mention in the updates to inform them
Description -Currently, on a project/task users can upload multiple documents with the same name. e.g. if you have two documents on your local machine with paths: folderA/asset.jpg, folderB/asset.jpg, you can upload them both and they will be present on the task/document. We would like this functionality for request briefing forms as well, please.Why is this feature important to you - Teams currently receive assets from suppliers with the same name but in different folders. It would speed them up a lot if they were able to upload all these assets without having to rename them.How would you like the feature to work - You select two assets from different folders with the same name and they are both uploaded successfully to the brief.Current Behaviour - Only one asset is uploaded
Description - These days in Launch's Web SDK extension, it is not possible to manually override the "_id" attribute in Web SDK XDM object data elements. As a workaround, if one wanted to manually define this _id, one would have to code an alloy "sendEvent" and specify the _id there. The approach / idea resembles very much the hybrid tracking approach for client- and server-side, that many 3rd party vendors suggest these days, where a deduplication key can be specified that either drops or merges events with duplicate ids. Why is this feature important to you Completeness of data and fastest possible data availability: Web SDK data relies on cookie consent which may not have been given by the users i.e., an order event may or may not be captured by the Web SDK this lack of order data significantly impacts the number of addressable members in an audience, that may be built upon CRM and commerce data while this commerce data can also be streamed into the Platform from the commerce or CMS backend through an HTTP API call, this will still likely be slower than the Web SDK data if you need it for immediate personalization (e.g., recommendation) but due to the immutability of Experience Events, sending order data from two sources, Web SDK + Commerce will affect the order events and revenue numbers in the CDP and connected analytics sources. right now, there is no deduplication key like other vendors provide in their Conversion API now, if we could manually specify the same _id attribute for all data sources, which ever event comes in first wins, and the other(s) with the same _id will be ignored in the CDP profile (while they are still floating around in the datalake) How would you like the feature to work Either implement a deduplication key feature like other Conversion APIs or allow the _id to be manually overridden (with a clear warnings about the possible implications) Current Behaviour The UI shows a big warning "The value for this field will be auto-populated when this data element is provided as the XDM object for a Send event action. This value cannot be overwritten."
Description This question has come up multiple times in the last few weeks, and it probably surfacing in other channels as well, but there should be a way to filter the rows in a freeform table based on Metric Count. So only show items below X, or above Y, or between X and Y. While we can filter rows manually via the "only show these rows" the values can change month to month, being able to only show rows based on a specific criteria seems like a basic function we should have, and yet don't as of yet. Why is this feature important to you Values change month to month, so having to manually find and filter rows is a lot of effort that we shouldn't need. While, yes, we can use a calculated metric to change rows outside of a range using IF and Greater Than/Less Than logic (using a static 0 for outside our range), the rows, while no longer counting in the total, still show in the table. How would you like the feature to work Either in the dimension filters, or possibly in the metric column settings, there should be a way to add a metric threshold filter: [metric] Greater Than (or equal to) X and Less Than (or equal to) Y, or just Greater Than (or equal to) OR Less Than (or equal to) Current Behaviour Today we can only filter by text matches, there is no equivalent feature.
Description - as soon as an Audience is created that is using aggregation e.g., to evaluate a certain number of page views with a given property like a content category, the only working evaluation is "Batch" which is obviously not suitable if you want to do next page personalization based upon a user's content affinity. Why is this feature important to you - It seems to be a standard feature in nowadays' CDPs to be able to define some kind of real-time "Badges" based upon user behaviour which can include aggregated values.This would be exactly that. Audiences on the Edge should support this as well since Batch evaluation is just too slow for next-page personalization. How would you like the feature to work - Allow aggregation on Edge or Streaming Audiences to be closer to real-time Current Behaviour - Upon save, an error is shown and none of the available segmentation methods works except for "Batch"
Currently, if you share an audience to e.g. Facebook Custom Audience, you can do only a 1:1 mapping of your xdm schema field. As some destinations have specific requirements, it would be great to have like a calculated field as an option (same as in datastream mapping). One example would be to lowercase your xdm schema fields, as e.g. Facebook Custom Audience needs firstname / lastname in lowercase. As of now, I have to ingest an additional field with lowercase firstname / lastname to make it happen (or do some query service magic). I guess some simple adjustments / transformations of your current xdm schema fields would be very helpful.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
