Build better products with our product team
Request for Feature Enhancement (RFE) Summary: I would like AEM to create custom renditions on the fly instead of when the asset is uploaded and processed. Use-case: I would like our users to be able to choose the specific rendition(s) they'd like to download in AEM. Currently in AEM if we create custom renditions AEM creates those renditions when the asset is uploaded and processed. If a user wants to download an asset they can download ALL renditions or just the original. I would like to see these renditions only occur when the asset is being downloaded instead of when its processed. So when a user clicks to download an asset they would be prompted to choose how they want it delivered to them and then the system would render it out on download. This is a cleaner experience for the user and doesn't take up storage in the DAM with a bunch of renditions that may not be needed. Taking this question further, I would also like to see this feature carry through to Asset Link. Currently there is no way at all to select renditions in Asset Link. It would be great if users could select the rendition they need when they are linking to the asset. Current/Experienced Behavior: Renditions created when asset is uploaded and processed. Improved/Expected Behavior: Rendition(s) can be selected specifically by users when downloading or linking from Asset Link and then processed at that time. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Dario Mescia/Enterprise Mobility Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: I would like to change the backend storage of assets based on its metadata while keeping the assets where they are in the DAM. Use-case: I would like to set up a property called Archive with a yes checkbox. When the box is not checked the asset is stored in active storage on the backend. When the status box is checked the asset is moved to glacier storage in the backend. So the asset stays in the same location in the DAM interface but the storage of it on the backend is dependent on the metadata in one of the properties. Current/Experienced Behavior: Archived assets are moved to a folder and all assets in that folder get moved to glacier storage on the backend. Improved/Expected Behavior: Backend storage is based on the metadata of an asset instead of what folder it is in. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Dario Mescia/Enterprise Mobility Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Display jcr:score next to result path in Query Performance Use-case: When using Query Performance to analyze a query sorted by jcr:score, it would be very useful to display for each of the result its jcr:score generated during the query execution.That would allow better understanding of the final results whenever query results are sorted by jcr:score and also make index management and lucene boosting evolutions much more predictible. Current/Experienced Behavior: Currently, only the paths of the results are displayed. Improved/Expected Behavior: With this feature, there would be two, one for the asset paths and one for the jcr:score Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Benjamin Jacquet / Accor Hotels Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Enable customers to programatically create task for the Asset Essentials task board Use-case: Upon asset expiry, we want to automatically create a task to the asset creator's task board in Asset Essentials. The asset creator needs to take action (re-approval, retire, etc.) which will be performed through an App (built using App Builder). Current/Experienced Behavior: No API exists allowing us (customers) to create tasks programmatically which are available to users in their task board Improved/Expected Behavior: Have the ability to create tasks programmatically (through the internal Collaboration API) Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Pfizer Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Use-case: Composite metadata is needed for store information which follows a Map format. Like: - key1: val1, val2 - key 2: val2, val3, val4 .... key n Current/Experienced Behavior: Composite metadata is only available for Pages. Improved/Expected Behavior: Composite metadata should also be enabled for Assets Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name: Mondelez Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: This ticket addresses issues with the AEM asset timeline and revision tracking not displaying all changes, focusing on understanding limitations and potential solutions. Use-case: Karen Barton (AWC Librarian) reported that asset overwrites by Jeff Hess were not shown in the timeline, causing tracking frustration. Sainikhil Reddy (Bounteous Dev) explained AEM timeline shows workflow/publication events but not all low-level edits without custom versioning or audit listeners. Sarah Scalia (Bounteous) noted implementing such custom workflows in AEM as a Cloud Service is complex, estimated as a 15-point effort. The asset metadata like "Modified" and "Modified By" is visible in column and list views but not in card or insight views. Current consensus is that timeline limitations are due to AEM core behavior; custom solutions would require significant development effort. Current/Experienced Behavior: timeline does not show all levels of changes Improved/Expected Behavior: timeline should show changes of any capacity to each asset Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets Cloud Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Description - Deadline reminder notifications aren't being sent to the assigned to user after the task constraint is changed before the task is due during the lift of the project. I had submitted a case with Adobe Support and they concluded that changing the task constraint while the project is current blocks the user assigned to the task from receiving the deadline reminder that is set up in the automatic reminder section. It would be helpful to have the deadline reminder notifications to still be sent to assigned users of tasks even after the task constraint is changed during the life of the project. Why is this feature important to you - Users are losing track of tasks they need to complete after the task constraint on tasks their assigned to is changed. They no longer received the system deadline reminders which is causing them to miss completing those tasks on time. We strive to have tasks completed by their planned completion dates regardless of the task constraint set. How would you like the feature to work - Deadline reminders we've set up in the system should still be sent to the users assigned to tasks even after the task constraint is changed while the project is active. Current Behaviour - Deadline reminders aren't being sent to assigned users of tasks after the task constraint is changed while the project is active.
DescriptionWhen using the Adobe Analytics API 2.0 to pull the details of our evars, we also need to know the expiration type and merchandising evar status. Why is this feature important to youWe're currently migrating our projects that use Adobe Analytics API 1.4 to API 2.0, but this latest version doesn't return whether an evar is set as merchandising and what its expiration type is. This feature used to exist in API 1.4, and we still need it as we use the API to keep our documentation up to date. How would you like the feature to workInclude the following key/value pairs in the response:"expiration_type": "page_view","expiration_custom_days": "1","merchandising_syntax": "product","allocation_type": "merchandising_last" For example, evar25 should return this: { "id": "variables/evar25", "title": "Internal Campaign Name (Product Syntax) (v25)", "name": "Internal Campaign Name (Product Syntax) (v25)", "type": "string", "category": "Conversion", "support": [ "oberon", "dataWarehouse", "realtime" ], "pathable": false, "extraTitleInfo": "evar25", "segmentable": true, "reportable": [ "oberon" ], "supportsDataGovernance": true, "description": "The ID of an internal promotion placement being impressed upon or clicked. Used to understand internal promotional conversion rates. Format {campaign type}:{campaign name}:{campaign location}", "multiValued": false, "expiration_type": "page_view", "expiration_custom_days": "1", "merchandising_syntax": "product", "allocation_type": "merchandising_last" } Current BehaviourIn the current version of API 2.0, there are no details about evars' expiration types and merchandising settings.
Description:All admins are currently receiving the notifications: Contributor user limit reached or Guest user limit reached. Why is this feature important to you:We do not need all admins to receive every notification. This can lead to unnecessary distractions and clutter in their inboxes. How would you like the feature to work:Implement a feature that allows selective notification settings, where we can choose which admins receive specific notifications based on their roles or responsibilities. Current Behavior:All admins receive all notifications without the option to selectively choose recipients.
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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK