Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: Would like a way for users in author instance to reset their password if they forget it. Use-case: author forgets their password and resets it via the AEM UI Current/Experienced Behavior: Requires manual intervention by a user-administrator Improved/Expected Behavior: User can reset password without intervention Environment Details (AEM version/service pack, any other specifics if applicable): 6.3+ Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Checking out an asset will also lock the metadata from being edited by other users Use-case: Prevent multiple users from editing the same asset including asset's metadata Current/Experienced Behavior: Check out an asset, another user can update the metadata for the checked out asset Improved/Expected Behavior: Check out an asset, another user can't update the metadata for the checked out asset Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP7 Customer-name/Organization name: General Motors Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: We were advised to only create 5 smart crops since there will be performance implications if there are more. THere's no limit in the UI but what Adobe said, we should not exceed 5  Use-case: Our organization needs a lot of smart crops since the assets in DAM are being used on different channels. Having a limit of 5 will make it difficult for us to support our customers;' needs Current/Experienced Behavior: Only 5 smart crops are requested to be created Improved/Expected Behavior: The system should have more capacity to accommodate more smart crops  Environment Details (AEM version/service pack, any other specifics if applicable): ACS Customer-name/Organization name: N/A Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: The Search and Replace feature only allows writers to search and replace content in the author mode. However, this does not resolve use cases where XML tags must be replaced across multiple files.  Use-case: The writer needs to replace a product name, which is in plain text, with a <keyword>.  Current/Experienced Behavior: Search and Replace only works in author mode.  Improved/Expected Behavior: Search and Replace can work in either author mode or source mode.  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Broadcom Inc.  Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: To have the Environment ie. Prod/Staging/Dev explicitly listed in the URL for AEMaaCS Use-case: Easier for end users to understand what environment their respective URL for the Author and Publish tier they are looking at. Current/Experienced Behavior: The current access URL is for the author is:https://author-pNumber-eNumber.adobeaemcloud.com Improved/Expected Behavior: The access URL for the author tier should be:https://PROD/STAGING/DEVauthor-pNumber-eNumber.adobeaemcloud.com It's far easier to understand which environment the URL relates too when viewed in a browser as people won't remember the p or e numbers. the same applies to the publish tier. 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: Enable users to sort pages and experience fragments based on name Use-case:   Current/Experienced Behavior: Pages/Experience Fragments are always sorted based on creation date.  Improved/Expected Behavior: Users should be able to choose to sort pages/experience fragments in column view based on the name of the item. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Amazon.com Employee Services Screenshot (if applicable): This is the feature available for assets in AEM 6.5.7   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Content Reference fields in a Content Fragment should update when references are moved Use-case: When Content Reference fields are used in a Content Fragment model, and populated in the Content Fragment to point to an asset or content, when this asset or content is moved, these Content Reference fields should update like any reference fields. Current/Experienced Behavior: When a content reference field is populated to point to an asset, and if the asset is moved, the content reference field is not updated. The Authors need to manually update these content reference fields to point to the new location of the asset. Improved/Expected Behavior: The content reference field should update when an asset is moved. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.7 Customer-name/Organization name: ANZ Screenshot (if applicable): Behaviour is available OOTB. Just add a Content Reference field

Hello, When creating a content fragment model, the data types "multi line text", “number field” and "enumeration" are missing the following properties:Mandatory flag for “multi line text” and “enumeration”Max. length for “multi line text” and “number field” We are using the latest 6.5 FP. Is it that feature on a roadmap ? Can we expect it in future releases ? Or should we request an evolution to add these fields ?Below is a snapshot showing the properties of the multi line text, we see that these 2 options are missing: Note: using the table kept deleting the content of my request so not using it...

Hello,our client is using the Multi-Site Management (MSM) features a lot.When checking component content in a live copy, they need to break the inheritance of the respective component first, so that they can access the component dialog. Afterwards they need to restore inheritance again.Business Value: This will reduce risks with accidentally not restoring inheritance and also will speed up the content QA process significantly. In AEM/CQ 5.6 (with Classic UI) it was possible to access/open the component dialog on a live copy with enabled inheritance.Can this be added to AEM?Thanks & Many regardsHendrik

Description -Currently offered CaaS feature allows content to be available as a Json for consumer systems. But there is no feature to either transform or update the DAM and Content links with the Absolute URL[Fully Qualified URL, Externalized URL with server details etc..] for either Content/Experience Fragments or  Custom Components with a single pattern/approach.Why is this feature important to you -It helps onboard the consumers system for readily consuming the contentEliminates custom logic at individual component level or customization for core components/exporter logic [For content/experience fragments]Leverage the recommended OOTB logic and have single pattern for content/experience fragment and custom components  How would you like the feature to work -Feature should have a enable/disable logic with configuration associated with itFeature should have a logic to allow transformation for specific patterns for links and configuration associated with itCurrent B

Content Fragments are now used widely in AEM project majorly in headless and hybrid model. But still there are some features that can be added in content fragment that can make it more valuable:1) Use of Multifield. Currently the multifield works fine when there is one level of child but for some cases we require multlevel multi field that does not work fine as it works in the component level.2) Live Copy Inheritance in Content Fragment is not supported.3) Asset level versioning shows the version number , it should also show the date of version so this will help to track the exact revision as well.4) Dialog level clientlibs instead of override dam.cq one for dialog level events.

Hi,A nice feature to implement will be a standard  "trash-bin" functionality for AEM Assets. Right now we have customization (implemented on AEM 6.3) as described herehttps://kbwebconsult.com/2020/07/21/the-enigma-of-aem-apache-sling-filters/ Best,Krass 

We would like to replace our web images with the google WebP format https://developers.google.com/speed/webp It would be great if webp could be supported in AEM Assets in near future.

As different client has different data archival standards, we need to create archival process for various clients. In AEM, since the content goes into the repository, anything that comes inside the repo becomes a data that is moved across environments. Moreover, we need to have a process for content editors for moving archived content to some other tree or space and to keeping the content tree clean and only with needed content. It will be great if you can support an archival strategy OOTB. The features I look for in this feature is1. Easy to manage from authoring experience2. Reduced to a small size3. It should be outside the repository so that we don't need to move that as content in the repo.4. We should be able to search through the metadata5. We should be able to retrieve the content with some action.

Since Adobe runs our AEM environment in AWS, we would like Adobe to make use of the AWS security features for my company.  Here’s the specifics:We want to use AWS STS to manage access to the companies Cognito service in AWS to get access to a JWT.  This is instead of using CryptoSupport.We would like to make use of AWS Secrets Manager and/or AWS Parameter Store to protect sensitive data.  We would like to use a Customer Managed Key provided by the customer for Secrets Manager and Parameter Store.Our objective is to not allow developer or Adobe support personnel from seeing any sensitive items like a password, api key, access credentials.  Since AWS has services that meet our needs, we would like Adobe to expose those services to us through the AEM authoring / administrative tools.

When we add absolute image url with preset having $, the css file will not load and throw exception from OOB code (com/adobe/granite/ui/clientlibs/script/Utils.java).  But by escaping $ we can overcome above issue and load the css file with preset correctly. .load {      background:url("https://scene7.image.com/is/image/adobe/someimageutl?\$native\$");}  

WHAT WE HAVE In AEM x.x.x version we have mechanism to check duplicate images being uploading in DAM which is supported by unique SHA1 value.This verification process is done during uploading of new Assets. 1. By enabling duplicate OSGI  asset service 2. OOTB mechanism is the SHA1 value check. Currently ,  other way of achieving similarity/ identical  is by using Sensei which will be based on tags but this process is again done AFTER successful Asset upload and enabling of SMART tags to specific folders. WHAT WE DO NOT HAVE We do not have mechanism where a Author WHILE uploading can know if there is any  similar / identical assets i.e. Assets which have been cropped or change in color shade etc. This should not be related to any property value check or SHA1 value instead check the pixels or any other parameter. AUTHORING Challenges use caseIn our current system we have thousands of pages with images of business leaders with differe

Creating adaptive forms via drag and drop bricks with a straight forward visual feedback (a bit like wufoo.com does, but adaptive!) – wouldn’t that be cool ?

Hello Team, We are using AEM 6.4.2 integrated with Dynamic Media. Here to fetch the URL of synced asset we are using com.day.cq.dam.s7dam.common.utils.PublishUtilsImpl.externalizeImageDeliveryAsset() by passing the resource object of the asset. We are seeing the unclosed resource resolver issue in logs. Please suggest. Any other way to fetch the DM published URL if not above? I suspect that in "com.day.cq.dam.scene7.impl.Scene7AEMBridgeImpl" resourceresolver might not be closed after processing. 14.10.2020 02:20:14.950 *WARN* [Apache Sling Resource Resolver Finalizer Thread] org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl Closed unclosed ResourceResolver. The creation stacktrace is available on info log level.14.10.2020 02:20:14.950 *INFO* [Apache Sling Resource Resolver Finalizer Thread] org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl Unclosed ResourceResolver was created here:java.lang.Exception: Opening

Hello,I am trying to install either experience manager or livecycle onto my MacBook Air.  I currently use Adobe Acrobat Pro. Can someone please help me? 

Description - Currently, we cannot use h2 and h3 in forms and have them appear on Generated Documents of Record. We have to use panel descriptions for blocks of form inputs, and cannot use in Static Text - they simply do not show and will block out the entire text block. To enable accessible scanning of form, we need to do a workaround of a panel descriptions for the DoR, but then put in the h2 and h3 for the Adaptive Form. Why is this feature important to you - Accessibility! Screenreaders scan by header levelsHow would you like the feature to work - support for <h2> and <h3> codes and other text formatting in static text that will show on DoR so we don't have to generate XDPs for legal static text. Current Behaviour -

Description - While uploading new assets from external system, those assets might contains some metadata properties. While uploading it to AEM, it's auto generating namespace and preserving those metadata. Which we would like to prevent using this feature request if possible, Only registered namespace metadata should preserve.Why is this feature important to you - It's creating issues while doing full text search and also impacting search speed. It certainly improve the system performance.How would you like the feature to work - Post implementation of these restriction that only registered namespace metadata will AEM allow , when we upload any asset from any external system, it will not create unnecessary namespaces automatically into system and also no unknown properties will be part of asset metadata and full text search will work fine.Current Behaviour - Currently if we upload assets from external system , if that assets have any metadata properties, while uploading on AEM , it's cr

Description - Any component that has a link field, edit dialog and click on the path finder. Search using search term or paste in a path in left rail path field to get to search results. Instead of only pages getting non-page "nodes" in the search resultsHow would you like the feature to work - When searched only pages should appear.Current Behaviour - Instead of only pages, showing non page nodes also. Thanks

Description - When a person is given Developer access they can pull and push to the Adobe Git instance for the program. There should be an option to prevent people with the Developer access to push when there is a customer Git repository that syncs to the Adobe GitWhy is this feature important to you - To prevent a customer Git repo becoming out of sync with the Adobe Git repo, there should be an option to not let people in the Developer role from pushing to the Adobe Git repo. How would you like the feature to work - Add an option to the Developer role to prevent pushing to the Adobe Git repo.Current Behaviour -

Description - We would like to create meta tags (not limited to keywords) on pages through page properties. We would also like to have meta keywords (tags currently in page properties) inherit to child pages or be able to set default tags.Why is this feature important to you - This feature would make tag management simpler and more manageable out of the box.How would you like the feature to work - Add tags through page properties in 2 sections, one for keywords and one for miscellaneous with an option to inherit to prepopulate and customize from there.  For example, if a user selects to inherit tags, it would prepopulate with the parent page's mete tags.  The user can then add tags or remove tags from their page as needed.Current Behaviour - Custom page properties and Java needs to be developed for this implementation of tag management