Product ideas | Community
Skip to main content

10000 Ideas

aanchal-sikka
aanchal-sikkaNew Participant

Enhancing AEM Assets ReportsInvestigating

Request for Feature Enhancement (RFE) Summary: Enhancing AEM Assets Reports with additional metadata fields that marketers can choose or deselect for generating reports would be advantageous. Furthermore, allowing marketers to create various asset report templates based on selected metadata and other criteria would provide even greater utility. Use-case: AEM Asset reports come with a predefined list of metadata that can be selected/deselected. Though custom metadata option is also available, but its technical. It would be good: - if the fields in the Asset Reports could be configured. - if a user could create an Asset Report template similar to Saved search and execute it when needed.  Current/Experienced Behavior: - Cannot add custom metadata as checkboxes as it lies in Internal Area  - Custom fields can be added buy defining exact property on Asset Report UI. Its too technical. Also, the configuration does not persist, thus one needs to configure it again before execution. Improved/Expected Behavior: It would be good: - if the fields in the Asset Reports could be configured. - if a user could create an Asset Report template similar to Saved search and execute it when needed.  Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5/Cloud Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

IndrajitSiNew Participant

Secure Cached Content is not working for first requestInvestigating

Request for Feature Enhancement (RFE) Summary: I have implemented permission-based caching for our secure site. The site will perform user authentication before serving any secure content. I have followed the document for configurations and implementation-https://docs.adobe.com/docs/en/dispatcher/permissions-cache.html  For initial request/cached content not available, the Dispatcher directly calls AEM resulting in displaying the secure page without authentication. Use-case: Use Case 1: The user must be authenticated via the Dispatcher Auth Checker Servlet before serving secure content. Use Case 2: If the user's authentication via the Dispatcher Auth Checker Servlet fails, the dispatcher will not forward the original request to AEM. Current/Experienced Behavior: Current Behaviour for Use Case 1: When the requested content is not cached, the Dispatcher Auth Checker sends the request directly to the AEM publisher for page rendering, allowing the user to access secure content without authentication. Current Behaviour for Use Case 2: If user authentication fails, the dispatcher forwards the original request to the AEM publisher for page rendering without authentication. Improved/Expected Behavior:  Expected Behaviour for Use Case 1: The user must be authenticated via the Dispatcher Auth Checker Servlet before serving secure content.Expected Behaviour for Use Case 2: If the user's authentication via the Dispatcher Auth Checker Servlet fails, the dispatcher should not forward the original request to AEM. Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Release - 2024.8.17465.20240813T175259Z Customer-name/Organization name: Boston Scientific (BSC)  Screenshot (if applicable):   Code package (if applicable):   @gurjotsingh @akashramchandani

IndrajitSiNew Participant

AEM Content Fragment New Editor issueInvestigating

Request for Feature Enhancement (RFE) Summary: I have implemented the composite Multifield in Content Fragment by referencing https://jimfrenette.com/aem/content-fragments/composite-multifield In this implementation, we have added custom Client-Libs for composite multifield and show/hide target functionality based on dropdown selection. These custom Client-Libs are loading correctly and working as expected in the old content editor. However, in the new content editor, the custom Client-Libs are not loading, causing the functionality to break.     Use-case: We have a dropdown, and on 3rd selection of the dropdown, multifield should show, and min value of multifield is 1 and max value is 5 Current/Experienced Behavior: When we open a new content fragment editor multifield is not getting hidden and giving a warning to add at least one item, as custom Client-Libs not loading Improved/Expected Behavior: In the New content fragment editor dropdown show/hide should work and also on the dropdown selection multifield items should show, Whereas in the old content fragment editor custom client libs are loading hence on the dropdown multifield is hiding and didn't get a warning Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Release - 2024.8.17569.20240822T203847Z Customer-name/Organization name: Bosten Scientific (BSC) Screenshot (if applicable):   Code package (if applicable):   @indrajitsi @gurjotsingh 

AG7New Participant

Decouple Stage and Prod cloud managed deploy pipelinsInvestigating

Request for Feature Enhancement (RFE) Summary: Here are some feature enhancments, these can be together or even just one of these implemented would solve a lot of problems 1.) Allow the selection of artifacts to deploy to production as one of the steps before deploying to production 2.) Decouple Stage and Production deployment pipeline.  Ability to deploy to Prod independently of deployment to stage 3.) Ability to start at production deployment simply by selecting previously built artifacts instead of having to start every time at the beginning of the pipeline. Use-case: Our product can contain ~171 modules which crashes the Adobe CM pipeline running the server out of resources. If the production publishers are overloaded the CM deployment fails to just one publisher it aborts the entire deployment.   In the above use cases if we can start from where we left off, or select the artifacts and maybe remove failing artifacts without starting over at the beginning of the pipeline that would improve efficiency.  Sometimes ou CM pipeline runs for 12 hours while it builds and deploys to production Current/Experienced Behavior: Unable to deploy to production and lack of robust pipelines Improved/Expected Behavior: Ability to deploy to stage and prod in parallel.  Ability to select artifacts to deploy to production without starting hte entire pipeline over again. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.21 Customer-name/Organization name: N/A Screenshot (if applicable):   Code package (if applicable):