Product ideas | Community
Skip to main content

10000 Ideas

Alexander_Geor1New Participant

AEMaaCS publish instances (Email service) should dynamically load their OSGi configs on update property event instead of relying on pod restartNew

Request for Feature Enhancement (RFE) Summary: Email service should implement an change event listener to re-read its oauth and refresh token properties when these gete updated ( /conf/global/settings/mailer/oauth) without the need of manual pod restart to re-read its value Use-case: Microsoft Azure oauth token is expiring every 90 days and its get automatically updated on author instance in AEMaaCS. This change is replicated to publish instances, but this change is ignored by the Email Service running on publish, because these properties are read only once when service gets initialized. So a manual restart of the pods is needed. Current/Experienced Behavior: When oauth token expired and gets updated with its new value all our form that send emails on all our live websites stop working, because the Email Service does not update its in memory value for that token, despite the fact that the token is already updated in the publish instance Improved/Expected Behavior: An event listener to update the memory value of the access token will solve this problem and mail forms will continue to work without any downtime and need of manual interaction Similar approach should be implemented to other services that have the same issue Environment Details (AEM version/service pack, any other specifics if applicable): AEM as as Cloud Service, support ticket with RCA of the problem https://experienceleague.adobe.com/home?support-tab=my-cases&case-id=E-001916327&org-id=22DA472D57D07A817F000101%40AdobeOrg#support Customer-name/Organization name: BBraun Medical Screenshot (if applicable):   Code package (if applicable):  

Rohan_Garg
Rohan_GargNew Participant

Automation mechanism within Developer Console or Adobe I/O Runtime Action to automatically renew the technical account certificateNew

Request for Feature Enhancement (RFE) Summary: Automation mechanism within Developer Console or Adobe I/O Runtime Action to automatically renew the technical account certificate (Case E-001849802) Use-case: We are using the service credentials JSON to get bearer token from IMS and then send payload over to AEM Author. The key concern is how to maintain this as the certificate expires after 1 year. Currently, we see the manual provision of generating a new certificate and then manually updating the runtime action with the service credentials. This approach is rather manual and crude. We would appreciate a solution that could automate this. Current/Experienced Behavior: As of now, Adobe does not provide an automated mechanism within the Developer Console or Adobe I/O runtime to automatically renew the technical account’s certificate. This means that certificate rotation must be triggered manually via the Adobe Developer Console. Improved/Expected Behavior: The certificate rotation can be automated to alleviate the load for manual setup of technical account certificates post their expiry.   Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Customer-name/Organization name: EPAM Screenshot (if applicable):   Code package (if applicable):  

bjoern__koth
bjoern__kothNew Participant

Launch Web SDK Extension - Define a custom _id attribute in Experience Event calls or a deduplication key for identical events from different sourcesNew

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."

DougMc4New Participant

Introduce a configuration (e.g., max.children.per.folder) that defines the maximum number of child nodes (assets or subfolders) allowed within a given folder.New

Request for Feature Enhancement (RFE) Summary: Introduce a configuration (e.g., max.children.per.folder) that defines the maximum number of child nodes (assets or subfolders) allowed within a given folder. Use-case: AEM currently allows more than 1,000 assets (child nodes) to exist within a single folder. However, it’s well known that exceeding this threshold leads to significant performance degradation. To help our administrators effectively monitor and control within our environment, we request the addition of functionality that provides both preventive and diagnostic controls related to folder child limits. This request covers two main objectives: 1) Prevent Adding Assets Beyond a Configurable Folder Child Limit 2) Expose a Method to Identify Overpopulated Folders Current/Experienced Behavior: None Improved/Expected Behavior: Requested Enhancements1. Prevent Adding Assets Beyond a Configurable Folder Child Limit Introduce a configuration (e.g., max.children.per.folder) that defines the maximum number of child nodes (assets or subfolders) allowed within a given folder. Enforce this limit across all methods of asset ingestion or modification, including: Author UI uploads (single and bulk) Programmatic or API-based imports (e.g., via custom integrations) Workflow-driven imports Package or Content Transfer installations When the limit is reached, block additional assets from being created under that folder and return a clear, user-friendly error message (e.g., “Folder has reached its maximum capacity of 1000 assets. Please create or use a subfolder.”). 2. Expose a Method to Identify Overpopulated Folders Provide a reporting mechanism or API endpoint that identifies folders exceeding the configured child limit. This could be implemented in one or more of the following ways: A built-in report under Tools → Assets → Reports An accessible QueryBuilder or GraphQL endpoint for integration with monitoring tools The output should include: Folder path Number of children Configured limit (for context) Optional recommendation for remediation (e.g., “Consider splitting into subfolders”) RationaleManaging folder size manually is error-prone and often discovered only after performance issues surface. Providing built-in enforcement and visibility would: Prevent system degradation before it occurs. Reduce administrative overhead of custom scripting or monitoring. Improve user experience by giving immediate feedback and guidance. Encourage scalable and maintainable DAM structures across all AEM environments. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Walmart US Marketing Screenshot (if applicable):   Code package (if applicable):  

KennyLarkinsNew Participant

Rich Text Editing Options for Tasks Details > Overview > DescriptionNew

Description - Enable Rich Text Editing for Task Details > Overview > Description.Why is this feature important to you - It would give us more tools to emphasize and communicate key details in the instructions and provide better readability for the user assigned to the task. Better readability means faster turnaround and fewer mistakes.How would you like the feature to work - Give us the same formatting options that are here in Ideas, i.e., preformatted styles, text color, text size, font, insert/edit code, insert video, create table, alignment, indent/outdent. Current Behaviour - Only plain text can be used, so instructions for tasks that are more complex are created in Word and uploaded, then a note is added to the task to see the attached Document for instructions which is less efficient for everyone.__________________________________________________________________________________________________ Here's a lot more UX friendly example (overly styled/colored for emphasis): Description - Enable Rich Text Editing for Task Details > Overview > Description.Why is this feature important to you - It would give us more tools to emphasize and communicate key details in the instructions and provide better readability for the user assigned to the task. Better readability means faster turnaround and fewer mistakes.How would you like the feature to work - Give us the same formatting options that are here in Ideas, i.e., preformatted styles, text color, text size, font, clear formatting, insert/edit code, insert video, create table, alignment, indent/outdent. Current Behaviour - Only plain text can be used, so instructions for tasks that are more complex are created in Word and uploaded, then a note is added to the task see the attached Document for instructions which is less efficient for everyone. Thank you for considering!   

rubenMNew Participant

Enhancement petition: Add an "Are you sure you want to stop the execution of the pipeline" pop up when deployingNew

Request for Feature Enhancement (RFE) Summary: Add a confirmation pop-up asking “Are you sure you want to stop the execution of the pipeline?” when deploying through Cloud Manager. Use-case: When deploying a pipeline through Adobe Cloud Manager, users can accidentally click the “Stop Execution” button instead of “Resume” during the deployment process. If this happens, the pipeline stops immediately without any confirmation, forcing the user to restart the deployment from the beginning.Although the package is reused and some steps can be skipped, this still causes unnecessary delays and confusion, especially in production environments. Adding a confirmation pop-up (e.g., “Are you sure you want to stop the execution of the pipeline?”) would prevent accidental interruptions and help ensure smoother, safer deployments. Current/Experienced Behavior: Currently, when a pipeline is running in Adobe Cloud Manager, the “Stop Execution” button can be clicked at any time during the deployment process.Once it’s clicked — even by mistake — the pipeline stops immediately without any confirmation or warning message. As a result, users must restart the entire process, even if the interruption was accidental. Although Cloud Manager reuses the same package, some steps still need to be repeated, which causes unnecessary delays and additional manual work. Improved/Expected Behavior: When a user clicks the “Stop Execution” button during a pipeline deployment in Adobe Cloud Manager, a confirmation pop-up should appear asking for verification before the process is stopped. The pop-up could display a simple message such as: “Are you sure you want to stop the execution of the pipeline?” Only if the user confirms the action (for example, by clicking “Yes” or “Confirm”) should the deployment be terminated.If the user clicks “Cancel”, the pipeline should continue running without interruption. This improvement would prevent accidental clicks from stopping active deployments and help ensure a smoother and safer release process, especially in production environments. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Cloud Manager – Production and Staging pipelines Example shown from Production deployment pipeline Current version and service pack are aligned with AEM Cloud Service latest release (SP23) Customer-name/Organization name: MITECO Screenshot (if applicable):   Code package (if applicable):