Adobe Experience Manager Sites

Request for Feature Enhancement (RFE) Summary:   In the Adobe SaaS platform, product detail and recipe detail pages are implemented using the CIF framework, meaning there are no physical pages for recipes and products. The current issue is the inability to identify internal references to specific recipe detail and product detail pages. Use-case: When we try to unpublish SaaS says there are Referenced pages but does not give the list of referenced pages, this is a serious limitation. This feature existed on the previous D2 platform. In Unilever platform some brands have over 800 pages and webmasters keep adding and removing pages on a very regular basis. There are many pages where Product URLS are also referred. Whenever a page or product is deleted or removed we do add 301 redirects. If there is an internal link if we don’t update those links then when user clicks on the link it redirects a new page url, This is being flagged by SEO error. Before unpubl

Request for Feature Enhancement (RFE) Summary: Currently we do not have any end point from where we can get all details of the article data .A few brands use the search api endpoints to fetch article data for a brand-locale but that only gives limited data ( title , body text , url ) .Currently we have systems like AIBA which use article data to train their models to generate dynamic recommendations . To do so we need some end point from article which when hit , directly provides all data in the body content of the article Use-case: A structured data feed with a periodic synchronization enables AiBA recommendation engine and AiBA LLM engine capability to have latest content and avoid any incorrect recommendations and also avoid a manual process for feeding the latest updates in article content.Other initiatives currently being discussed for LLM and AI engine revamp may also benefit from this implementation. Current/Experienced Behavior: Currently there is no provision in the pro

Request for Feature Enhancement (RFE) Summary:  Implementation of global find and replace functionality on TouchUI (AEMasCS) Use-case: Globally search & replace contents to helps during situation incorrect migration, Batch modification of content, clean up junk data injected from various Adblock browser plugins.  Current/Experienced Behavior: Not Implemented in AEMasCS but this feature was there in classic UI. AEM 6.5(previous version) Improved/Expected Behavior: Globally search & replace contents on AEMasCS Environment Details (AEM version/service pack, any other specifics if applicable): AEMasCS Customer-name/Organization name: Raja.T Screenshot (if applicable): Screenshot of AEM 6.5(previous version)   Code package (if applicable): com.day.cq.wcm.core com.day.cq.wcm.core.impl.servlets Servlet Name:  FindReplaceServlet.java

Request for Feature Enhancement (RFE) Summary: Implementation of Private Folder for AEM Pages. Use-case: We want to enable our Stakeholders option to assign privileges (read, edit) by their own. Think of it as a secondary ACL management, which is for individual stakeholders and is completely managed by them, for that we are looking for Private Folder option similar to AEM Assets. Current/Experienced Behavior: Private Folder feature only exists for Assets. Improved/Expected Behavior: Option for creation of Private Folder in AEM Pages. Environment Details (AEM version/service pack, any other specifics if applicable): AMS AEM (6.5.17.0) Customer-name/Organization name: Bhuwan Bhaskar Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Fail AEM cloud build if any critical or major code severity found Use-case: There should be a checkbox to enable or disable to fail the build if code severity found to keep code vernability free Current/Experienced Behavior:   Improved/Expected Behavior:   Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):        

Request for Feature Enhancement (RFE) Summary: When using asset-link, I can search for and use assets out of AEM directly in Creative Cloud Applications. But when I found an asset, I might want to check it's metadata, or check the folder it's in for other assets, and such. The asset-link UI is not good for such activities, and cannot do them.As such, it would be great to be able to directly open the asset directly in AEM - using the information asset-link already has to open the asset in the browser in AEM-ASSETS.Searching though cloudmanager for the right environment, then searching for the right asset inside of AEM is cumbersum and error-prone. Use-case: check/edit metadata of files used in asset-link review the folder the asset used in asset-link is in preview the edited  asset in AEM with renditions etc.  preview the edited asset in the experience the asset is for (website, etc.)  Current/Experienced Behavior: The asset cannot be opened in AEM using a

Request for Feature Enhancement (RFE) Summary: searching fo all licensed adobe stock assets  with the adobe stock connection in Assets Use-case: searching & saving all licensed adobe stock assets to internal DAM structure.  Current/Experienced Behavior: no search filter for licensed assets vailable in stcok interface Improved/Expected Behavior: filter "licensed " assets  Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service Assets , adobe stock integration Customer-name/Organization name: EON Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: it is not possible to remove users from AEM Groups after the have been removed from IMS groups Use-case: we are using AEM usergroups to send out email Informations to users. if the user leaves out company we remove the user from IMS groups. consequentely the user dont have access to AEM any more. but user is still part of AEM Usergroup , so will still receive emails Current/Experienced Behavior: As the user can't log in, no "sync" has been initiated to remove him from AEM groups. Consequently, the user in AEM is still part of all the groups he was in before being deleted from all IMS Groups. Improved/Expected Behavior: find a way so that users can be remove from AEM groups- manualy or automatic cleanu / sync  not relativ to users login Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service Assets Customer-name/Organization name: eon Screenshot (if applicable):  

Request for Feature Enhancement (RFE) Summary: Add Priority Queue in AEMaaCS Use-case: The customer is publishing bulk content via content tree workflow. When the bulk contents are in the queue, there is a delay if we publish any content directly via the quick publish button option. Current/Experienced Behavior: Delay in publishing the priority content Improved/Expected Behavior: Content publishing will be faster for priority content Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: LGE - APAC Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: enhance feature set for AEM Asset Reporting  Use-case: We propose the implementation of a new features in Adobe Experience Manager (AEM) that allows users to create custom report templates for asset management. These templates can be saved and scheduled to run at user-defined intervals, such as monthly. The primary purpose of this feature is to facilitate the generation of reports that scan for assets scheduled to expire within a specified timeframe and defined meta data parameters. Key Features: Custom Report Template Creation: Users can create and save custom report templates and use again. Templates can include custom metadata fields configured by the user. Scheduling: Users can define a schedule for the report to run automatically, such as daily, weekly, or monthly. Email Delivery: Users can register one or more email addresses to receive the generated report. The report can be sent as a PDF attachment or as a link to

Request for Feature Enhancement (RFE) Summary: Currently, Web Tier and Frontend pipeline deployments are not supported on AEM Cloud RDE instances. Use-case: AEM RDE instances make faster deployments possible but if team is using Web Tier and Frontend pipeline then there is additional change needed to maintain different configurations for RDE v/s non-RDE instance. e.g. Deployment to RDE mandates running full-stack build to deploy frontend and dispatcher code which would otherwise be going through separate pipeline on non-RDE instance. Current/Experienced Behavior: Currently, Web Tier and Frontend pipeline deployments are not supported on AEM Cloud RDE instances. Improved/Expected Behavior: Web Tier and Frontend pipeline deployments should be supported on AEM Cloud RDE instances. Environment Details (AEM version/service pack, any other specifics if applicable): Latest AEM Cloud version Customer-name/Organization name: Abbott Screenshot (if applicable):   Code packag

Request for Feature Enhancement (RFE) Summary: When a server fails to successfully deploy the pipeline aborts leaving servers in various states of deployment. Instead when a publisher fails, the failed publisher/dispatcher pair should be left out of rotation and the deployment should continue to the next server. A notification/incident is sent/created to CSE and customer. In an environment where there are 10 publisher/dispatcher pairs one server or even multiple servers failing can be left out of rotation and still serve proper traffic. The aborted pipelines in this case cause 8-9 hours of delays, sometimes days to resolve. This costs all parties a significant monetary and time loses. Please create a JIRA ticket and request for this. Keep me posted on when that is created and share regular updates on the progress of the request Use-case: In large infrastructures deploys can take 9-10 hours to completed.  One failure can cost hundreds of thousands of dollars in delays that can

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 b

Request for Feature Enhancement (RFE) Summary: Search Result Landing Page Use-case: Improve Search UX Current/Experienced Behavior: When a term is searched in the header/search component a list of links is returned Improved/Expected Behavior: When a term is searched in the header/search component a landing page with the search result is returned. In that page is possible apply filters and sort the results. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Adobe AEM Screenshot (if applicable): Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Automatic Deletion of Merged Feature Branches from Adobe Git Use-case: We have a sync job that syncs organization-specific branches to Adobe Git. This job performs deployments to AEM Cloud as a Service Dev instances for testing and validation. Once the testing is complete, the corresponding feature branches are merged into the Main branch, which triggers deployment to AEM Cloud as a Service stage/Prod. However, the feature branches are not being deleted from Adobe Git after the merge, leading to clutter and potential confusion. Current/Experienced Behavior: After merging feature branches into the Main branch, these branches are automatically deleted from our organization’s repository. However, they remain in Adobe Git, which creates unnecessary clutter and can lead to potential errors. Improved/Expected Behavior: Feature branches should be automatically deleted from Adobe Git once they have been merged into the Main branch, mirror

Request for Feature Enhancement (RFE) Summary: Rollout config "Activate on Blueprint activation" does not work for preview publisher node Use-case: Publishing Language Master instance of a page doesn’t publish the children/live copies. The children (IE, NI) need to be published individually to replicate to preview."Activate on Blueprint activation" rollout config has been set up but this only replicates to publish nodes. Current/Experienced Behavior: By default, any activation from the author only goes to publish and not preview. Improved/Expected Behavior: The replication must occur for preview node as well as this is also a publisher instance. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service Customer-name/Organization name: Brown Thomas Arnotts Screenshot (if applicable):   Code package (if applicable):  

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 con

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 w

Request for Feature Enhancement (RFE) Summary: Log Forwarding Option available for Amazon CloudWatch Use-case: Our client is using internally Amazon CloudWatch https://docs.aws.amazon.com/cloudwatch/ for all applications and would like to use that solution as well for AEM logfiles. I am well aware that AEM supports logforwarding using Splunk. On recent documentation https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/log-forwarding more logging destinations are documented. In case this will be part of an early adopter program, our client is interested in participating. Current/Experienced Behavior: No options are available for Amazon CloudWatch logforwarding Improved/Expected Behavior: An option will be made available Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Valtech. (Client doesn't want to be named in public) Screens

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