Adobe Experience Manager

Many customers today need the AEM Versions to be kept and not purge due to legal requirements.At any given point of time , customers may want to restore to any previous versions, can view differences, go in timewarp mode with all the previous versions of a page. Over a period of time , the jcr:VersionStorage can grow to more than 100 million nodes which makes indexing , Inplace Upgrade and overall system performances slow. We need ability in AEM where jcr versions can be offloaded to an offloaded instance / shared mount and all the OOTB functionalities like Restore, TimeWarp, Version history / difference should work AS IS without the need of custom code/ implementation.

Hello,our client is using the Multi-Site Management (MSM) features a lot.In a live copy, only a full page can be synchronized with the source.As rolling out a component to the live copies is possible already, they would like to have a feature for synchronizing a page in the live copy on component level as well.Business Value: This will reduce risks of publishing non-approved content and also will reduce communication effort within the editorial team.Can this be added to AEM?Thanks & Many regardsHendrik

Request for Feature Enhancement (RFE) Summary: Is it possible to increase the selection or clickable area on an asset or folder rather than enabling the selection only on the thumbnail area? Use-case:   Current/Experienced Behavior: Selection allowed only on thumbnails Improved/Expected Behavior: Clicking anywhere on the folder or file name should select the same Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.4 service pack 7 Customer-name/Organization name: Oxford Properties Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Only titles can be added to smart crops and renditions which can make it hard for consumers to know when to use a rendition and what is it for (e.g. page components, channels, pages) Use-case: If the renditions list is long, it's confusing for users to know what reset to use for a certain use case Current/Experienced Behavior: Descriptions cannot be added to renditions Improved/Expected Behavior: Add the ability to add renditions Environment Details (AEM version/service pack, any other specifics if applicable): ACS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: No granular control of access to a specific fields/group of fields by users/groups (i.e. not all or nothing to edit metadata) Use-case: Currently, we cannot prevent users from updating a certain field only or groups of fields in the properties. It’s either the user gets to edit all or none. This impacts creative rating and commenting. Ideally, we would want to allow asset consumers to be able to post comments or reviews, rate assets but not edit any metadata. Due to this existing restriction, only our group librarians can do that. Current/Experienced Behavior: No flexibility to set-up granular permissions Improved/Expected Behavior: Be able to set-up granular permissions Environment Details (AEM version/service pack, any other specifics if applicable): ACS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Publish to AEM option cannot be hidden Use-case: Even if we don’t have a publish server, we cannot unhide the publish to AEM button Current/Experienced Behavior: Publish to AEM option cannot be hidden Improved/Expected Behavior: Have the ability to hide the publish to AEM button  Environment Details (AEM version/service pack, any other specifics if applicable): ACS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Custom Tag predicates cannot be permanently configured to only pull specific namespaces Use-case: We want to have multiple tag fields not just one Current/Experienced Behavior: AEM has an out-of-the-box tag field. There are certain instances wherein stakeholders would like custom tag fields configured for certain tag groups. E.g. A tag field for “Content Type”, “Target Country(ies), “Campaign”. In the schema editor, there is no out-of-the-box way to limit what namespace is going to be displayed on a certain tag predicate. With that, even if there are multiple tag fields created, all of them will display the same set of tags or tag groups Improved/Expected Behavior: Have the ability to point tags fields to a specific namespace Environment Details (AEM version/service pack, any other specifics if applicable): AEMAaCS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable): &

Request for Feature Enhancement (RFE) Summary: As a general user, I'd like to have a "recently used tags" feature that suggests tags in the textbox so that I don't have to remember what I previously used Use-case: A user is adding an asset and wants to add tags to it.  Current/Experienced Behavior: User has to pick tags manually Improved/Expected Behavior: A list of tags that have been recently been added will appear and user will be able to select tags for the asset they are working on.  Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2021.7.5607.20210705T063041Z-210600 Customer-name/Organization name: Accenture  Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Add (optional) approval step (or something similar) before deploying to a Dev or Stage environment Use-case: The environments are used by a different company to test the software and therefore requires alignment of the deployment maintenance. As the build time could vary a lot, this maintenance window needs to be quite large. (With this option the 15 minutes of the deployment step + 10 minutes smoke test as maintenance window would already be sufficient as the pipeline and its long running build and unit testing steps could be started much earlier.) Current/Experienced Behavior: After "Code Scanning" step the pipeline will immediately start deploying the new software package. Improved/Expected Behavior: Option to pause the pipeline before executing the deployment step. This option should be available for non-production as well as production pipelines. Environment Details (AEM version/service pack, any other specifics if applicab

Request for Feature Enhancement (RFE) Summary: As a user, I prefer to see a “relate” function at the top ribbon for ease of use. Use-case: When working with assets, have the ability to access the "relate" function from the top ribbon Current/Experienced Behavior: The "relate" function can only be accessed from the ellipse on the properties screen when working with an asset Improved/Expected Behavior: The "relate" function will be moved to a more prominent place on the top ribbon  Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2021.7.5607.20210705T063041Z-210600 Customer-name/Organization name: Accenture Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Bring back the creative rating field with "stars" in AEM Cloud Use-case: Right now, the creative rating field is a textbox that accepts numeric values. This was not the UI in AEM 6.5 It's hard for our users to rate assets because of this since they don't know the limit Current/Experienced Behavior: The creative rating field is a textbox that accepts numeric values. Improved/Expected Behavior: Bring back the "star" field for creative rating 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: Struggling to upload a directory full of assets into AEMaaCS from my Mac OSX laptop. Assets were pulled directly from a dispatcher cache, so they are all valid AEM filenames. AEM Desktop App 2.1.2. Issue: Any time a failure occurs, the upload operation can't be resumed, it just spins forever. The only way to move past this is to fully exit the app and restart it. There should be a way to recover from this scenario - the app should not appear to still be doing work when it's already aborted the operation.   Use-case: Content migration from AEM On-Prem to AEMaaCS. Content Transfer Tool did not work, so Desktop App and Package Manager were the only remaining options. Current/Experienced Behavior: App appears to still be doing work even though all app activity has ceased due to the error Improved/Expected Behavior: App should properly reflect the status of the current operation. It should also should warn that an e

Request for Feature Enhancement (RFE) Summary:   Use-case: Allow images for field description e.g. https://aemlab.blogspot.com/2021/05/aem-touch-ui-component-dialog-fielddescription-image.html Current/Experienced Behavior: Rich Text gets encoded and does not render HTML Improved/Expected Behavior: Rich Text should be supported for dialog field description property Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 and AEMaaCS Customer-name/Organization name: N/A Screenshot (if applicable): More details at https://aemlab.blogspot.com/2021/05/aem-touch-ui-component-dialog-fielddescription-image.html Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: One-click support ticket with attached telemetry for CM pipelines that fail after maven and code check stages Use-case: AEM Customers in the support admin role should be able to provide full context including transient environment state for CM and Cloud Service product engineering when a pipeline failure occurs, independent of CSE intervention/ticket triage.When non-deterministic pipeline failures occur, the chain of escalation is Customer -> CSE -> Product Engineer. Invariably, the Product engineer needs to be able to review transient pipeline state in order to be effective in identifying root causes that may or may not originate with product bugs. The escalation process, however, often takes enough time that the transient state is lost due to factors outside the control of the customer or CSE involved in the initial response. Because the identification and collection of the transient state artifacts is easily performed, and pe

Request for Feature Enhancement (RFE) Summary: Would be nice to see in the UI the user who started the pipeline execution Use-case: Sometimes admins need to do audit or troubleshoot pipeline executions. In the case of a situation where a pipeline was triggered unexpectedly it would be good to know who triggered the pipeline so that the necessary actions can be taken like removing access if the user was in a role they shouldn't be in.  Current/Experienced Behavior: Currently information on who started the pipeline can only be retrieved using the API  on https://www.adobe.io/apis/experiencecloud/cloud-manager/api-reference.html#!AdobeDocs/cloudmanager-api-docs/master/swagger-specs/api.yaml . This would only give the Adobe Identifier which requires another step of finding the email or username either using another API call or by using the  admin console to map it back to the username. Improved/Expected Behavior: Show the user name who started execution in the

Request for Feature Enhancement (RFE) Summary: I'd like to request that the dispatcher flush is done prior to a deployment/pause.  This will facilitate testing during the pause.  It would be fine to then again clear the cache as it does today when the pair is reattached to the load balancer. Use-case: When testing during a deployment/pause it is beneficial to have the dispatcher cache cleared to ensure we are testing against the current code and not something in the cache. Current/Experienced Behavior: We need to request our CSE to flush the cache during the deployment/pause. Improved/Expected Behavior: Doesn't require the CSE to flush the cache during the deployment/pause. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5 AMS Customer-name/Organization name: NEW YORK LIFE INSURANCE COMPANY Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Localized Reference for Experience Fragment Use-case: We are using AEM 6.4.8/6.5.8 and using experience fragments component in our page templates for header and footer implementations similar to WKND sites. In template, we add experience fragment component with "/content/experience-fragments/us/header" as fragment path and when we create pages in /content/<project>/us/page, we are able to see the US Header.   Now we created language copy of the experience fragment to "/content/experience-fragments/fr/header", and now created page under "/content/<project>/fr/page", due to Localization implementations in experience fragment core component, automatically FR header is picked up on the FR page. Current/Experienced Behavior: Now US Team, changed something in US header and planned to publish sometime next week. parallelly FR team changed some page content and when trying to publish FR page, it is showing US Header as o

While designing cq:dialog we generally use CRXDE or we update the _cq_dialog/.content.xml file. But there is no feature like designing metadata schema or CF model for cq:dialog. There should be a feature called Design Component Dialog using drag n drop.

Description -The Authors would like to apply colors to the content/text that is added to a web page.Currently an out of box option does not exist.Why is this feature important to you - It will make all our Author lives easy, While applying colors to the context/text.How would you like the feature to work - The Authors should able to select the colors to the context/text.Current Behaviour - Currently we are using 3rd party color-picker plugin and it is not working as expected.

Request for Feature Enhancement (RFE) Summary: Order of menu bar options should be unique in all scenarios , please find example below. "When you select from a folder, they are ordered CREATE - SHARE LINK - DOWNLOAD - CHECKOUT - PROPERTIES - TO COLLECTION - etc. In a  search selection, they are ordered PROPERTIES - SHARE LINK - TO COLLECTION - DOWNLOAD - CHECKOUT - etc." Having to constantly search for options that are in a different location makes for inefficient navigation.  Use-case: Visibility of menu bar option in fix order in all scenarios / views. Current/Experienced Behavior: Options are not in order if we consider scenario of select searched assets vs navigate to folder and select asset, if you compare menu bar option order , it's not the same. Improved/Expected Behavior: Options should be in one unique order.  Environment Details (AEM version/service pack, any other specifics if applicable): 6.5.7 Customer-name/Organization name: Hershey's Scr

Request for Feature Enhancement (RFE) Summary: With more and more increased usage of Content Fragment for Headless applications (who consume JSON CFs from AEM), there is plenty of requirement where application teams need more control on each fields in Content Fragment. Currently there is no option to add custom field validations, add javascript validations or Regex in Content Fragment. Use-case: Content Authors make mistake where they save and publish critical data in CFs. Need custom validation logic option to be added in each datatype so that we can add more checks. Current/Experienced Behavior: No validation logic in datatypes except very basic like Required. Improved/Expected Behavior: Validation logic for each datatypes and among different datatypes in each content fragment model. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.5 Customer-name/Organization name: Manulife Screenshot (if applicable):   Code package (if

Request for Feature Enhancement (RFE) Summary: CF editor with tabs Use-case: Customer has complex structured contents, modeled by CFs. Each CF has more than 50 different attributes (data types). Some of them also custom , like you can model with sub-fragments through the Content Reference. Editing these models with the CF Editor is not easy and requires to open different tabs on browser to have the complete picture. Our request is to have the possibility to split the various attributes on different tabs, like the metadata editor actually does at the moment. Current/Experienced Behavior: complex contents (with 50+ attibutes) must to be splitted in different CFs and authored separately Improved/Expected Behavior: a single CF Editor component with the possibility to separate attributes in tabs (which mimic the current Metadata editor) Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service, 2021.2.xxxx Customer-name/Organizati

Description -Currently, the content fragment model editor does not contain a radio data type.Why is this feature important to you -Most of the time content fragment contains some data like selecting gender. for this kind of work, we have to use the dropwon data type.for refrennce,I have written one blog for a similar kind of feature just to add color picker data type.https://blogs.perficient.com/2020/10/20/adding-a-color-picker-to-the-aem-content-fragment-model-editor/

Request for Feature Enhancement (RFE) Summary: A feature that can allow users to select and complete multiple inbox items. Use-case: Different assets in AEM DAM are getting submitted through workflow for librarian to review and publishing activity. Right now, Approver has to select single item in inbox and complete it. This process needs to be repeated for each workflow item in inbox Current/Experienced Behavior: Right now, We can select and complete single approval workflow item from AEM inbox. Improved/Expected Behavior: Allowing users to select multiple workflow items (same workflow process with different payloads) and complete(Approve) them one go instead selecting each item and completing it Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name: Hershey Screenshot (if applicable): NA Code package (if applicable): NA

Request for Feature Enhancement (RFE) Summary: The HTTP Assets API should also capture metadata such as lastReplicated date. Use-case: The HTTP Assets API endpoint will be consumed by channels. (Apps, Salesforce etc). The need for this lastReplicated date is so that channels only retrieve the Content Fragment (CF) if it has changed, if not, the cached version at their end is used.  This would be a good feature add to consider. Current/Experienced Behavior: The HTTP Assets API does not contain the lastReplicated date for the CFs. Our channels consume this endpoint. Because the lastReplicated date is not available in this API, we need to build a custom solution that provides this piece of info to Channels as another API. Improved/Expected Behavior: The HTTP Assets API will contain the lastReplicated date metadata for the CFs, so channels only retrieve the CF if it has changed. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.