Adobe Experience Manager

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

Description -This feature helps the distributed authors be able to view tags in their localized language when they've set their language preferences as part of their user profile. How would you like the feature to work - This feature would display the localizations for tags vs the Tag Title when the Author's language profile is set to their local language and the localization is provided.Current Behaviour - The system currently displays the Tag Title regardless of user language setting and regardless of whether their is an available translation.

Hello,our client would like to have the ability to edit a page with enabled Live Copy Status view. This was possible with AEM 6.1.There are use cases where this is helpful, especially if there are a lot of components on a page and an editor needs to find and update the one with the broken inheritance.Can this be added to AEM?Thanks & Many regardsHendrik 

Hi All,In our day to day AEM dev life, we come across various requirements which demands us to create similar dialogs over and again. One such day a simple thought crossed my mind - What can make my life simpler?Below is the result of it --Request for Feature Enhancement (RFE) Summary :Ability to create the component & dialog from the author's instance.Use-case:Need to have author console/editor where developers can open that editor and start creating the component and dialog. Access should be given to the specific dev-users and only those users should be able to see the console and create the components. Able to provide the widgets similar to the metadata profile so that developers will just go and create the widget by drag & drop functionality. Ability to choose the root path of the project where the component needs to be created and other properties which are required for a component (eg., resourceType,component group). Current/Experienced Behavior:We cur