Product ideas | Community
Skip to main content

10000 Ideas

dmescia2
dmescia2New Participant

Creating renditions on the fly instead upon processingInvestigating

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):  

Jared_Mauch
Jared_MauchNew Participant

Allow Task Deadline Reminder Notifications To Be Unaffected From Task Constraint ChangesNew

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.

sartortiagoNew Participant

Return expiration type and merchandising evar status through Adobe Analytics API 2.0New

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.