Product Communities

Description - I would like to "watch events" for specific user in Fusion, or converse exclude from watching specific userID.  Why is this feature important to you - This would be huge resource saver and performance improvement for Fusion scenarios. Any upgrade to filtering capabilities limits the number of when scenario gets triggered. This saves customers operations, Fusion/Adobe resources, so the benefit is mutual.   How would you like the feature to work - have an option to include/exclude updates made to a given object type by a userID. This field is available in watch event output bundle, so I'm guessing adding this as filter option should be easy. Current Behaviour - We use service account to perform tons of operations in Workfront. Excluding this account in watch event modules is critical to limit the number of times scenarios are being triggered without a need. Worst case scenario is where ~90% of times scenario is triggered by service account updates and I

機能改善要求（RFE）概要： When editing a live-copied Content Fragment, please enable breaking inheritance directly in the New Editor. ユースケース： The author localizes the values of the live-copied Content Fragment. 現在／体験した動作： We have to switch editing modes to break inheritance, which is very inefficient. 改善／期待される動作： In the New Editor, I would like all the features covered by the traditional editor to be available, with additional new features added. 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）： AEM As a Cloud Services 顧客名／組織名 Kyocera スクリーンショット（ある場合）   コードパッケージ（ある場合）  

Request for Feature Enhancement (RFE) Summary: This feature will enable organizations to define metadata validation rules based on compliance or guideline requirements and extract detailed reports for discrepancies. This will facilitate better data governance and streamlined updates to metadata across the organization. Use-case: Organizations often face challenges ensuring metadata adheres to evolving compliance regulations or organizational guidelines. Manual validation processes are time-intensive and error-prone, leading to non-compliance risks and inconsistencies in metadata quality. This feature addresses the need for automated validation and actionable reporting. Current/Experienced Behavior: Metadata validation is performed manually or using scripts, leading to inefficiencies. There is no unified interface or reporting mechanism to validate metadata against dynamically defined compliance rules. Discrepancies or outdated metadata are identified late, causing delays in re

Request for Feature Enhancement (RFE) Summary: Currently we are unable to see the user who last modified the asset. There should be field where the user who last modified the asset should be captured. Use-case:   Current/Experienced Behavior: Unable to see the user who last modified the asset. Some hard coded value like "dam-workflow-service" is seen for now. Improved/Expected Behavior: Instead of "dam-workflow-service" username or user email who last modified the asset should be there. Environment Details (AEM version/service pack, any other specifics if applicable): Prod/Stg/Dev Customer-name/Organization name: Signify Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Allow customize wywisyg inline and richtext. At the moment is limited the wysiwyg and only allow some actions instead to use the full power of the wysiwyg. Use-case:   Current/Experienced Behavior:   Improved/Expected Behavior: With universal editor at the moment is imposible to customize or extend buttons for wysiwyg inline and richtext component. Should be fantastic to have configuration to allow hide/add new buttons in the wysywig. One simple thing as a color picker. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Santander Screenshot (if applicable):   Code package (if applicable):  

機能改善要求（RFE）概要： This is a consultation about applying custom CSS when authoring with AEM. The core component is designed so that you can only change the ID and cannot add classes.In terms of html validation, I don't think you can use the ID of each component when there are multiple identical components. However, in this case, the ID name will be unique and the same style will be written in CSS. Request the addition of the Class property in the core component dialog. ユースケース： Add Custom class CSS in core component dialog 現在／体験した動作：   改善／期待される動作：   環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）：   顧客名／組織名 Mitsubishi Electric Corp. スクリーンショット（ある場合）   コードパッケージ（ある場合）  

機能改善要求（RFE）概要： About the menu for text components As attached, only 5 icons are displayed at the top of the text component editing screen. If you display it in full screen, more icons will appear. With the current specifications, you cannot tell if there are multiple icons unless you use the full screen.Very difficult to understand. Request that all types of icons be displayed even if it is not full screen. ユースケース： menu for text components 現在／体験した動作：   改善／期待される動作： view all icon 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）：   顧客名／組織名   スクリーンショット（ある場合）   コードパッケージ（ある場合）  

Request for Feature Enhancement (RFE) Summary: Rework the Translation Projects in a way that also normal users (and not only administrators) can see the members which are also assigned to the project in the tile "Team". Use-case: As a user who starts translation projects, I want to see who else is member of the translation team. And, with which rights. Current/Experienced Behavior: Only member of administrators group can see all members in the "Team tile". The member itself are just seeing one member here - that's his account. System shows always "Team (1)" as title of the tile, which is wrong in this case. So, for the normal user this tile is completely USELESS (and shows actually wrong information in case there are more members). Improved/Expected Behavior: Tile "Team" in the Translation Project should show all members which are assigned to the team also for non-admin users! And, would be quite helpful if there would an hover effect on the avatar icon showing details of the

Request for Feature Enhancement (RFE) Summary: Rework the functionality how settings, which user can adjust, are saved. The current way to do that with a cookie avoid an efficient way of working for editors if they are switching devices and or browsers. Use-case: As an editor, I configure my AEM UI to my needs so that I can work most efficiently. So, e.g. I set up the left pane to show always the content tree. If I use another browser or switch the device, I'm working with, those settings should be still effective. Current/Experienced Behavior: Setting are not kept as the are stored not in the user account in AEM but in a cookie (which by the way expires also at next day, I think) Improved/Expected Behavior: Make those settings persistent in the user account within AEM so that it is not necessary to set them up every time. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Carl Zeiss AG Screenshot (i

Request for Feature Enhancement (RFE) Summary: Develop graphql sorting feature Use-case: If I want to sort graphql results by a name/number field alphabetically, current graphql doesnt support. Current/Experienced Behavior: If I want to sort graphql results by a name/number field alphabetically, current graphql doesnt support. Improved/Expected Behavior: Graphql should support sorting features for text or number or dates fields Environment Details (AEM version/service pack, any other specifics if applicable): All Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Idea Summary: The new Cloud Manager Content Fragment (CF) Editor does not support displaying custom field types such as ColorField, TextArea, and PathField, which were previously replaced in the classic editor. This lack of support significantly impacts users relying on these customizations for structured content authoring. We propose adding native support or a UI extensibility option to render these field types appropriately. Business Use Case: Organizations using AEM depend on custom field types to maintain structured content entry consistency. The inability to render these fields in the new CF Editor forces users to revert to the classic editor, limiting their ability to leverage new UI features. Providing native support for custom client-side renderers would enhance usability and encourage migration to the new UI. Current Behavior: The CF Editor does not recognize or display custom fields such as ColorField, TextArea, and PathField. Custom client-side renderers are ignored, mak

Request for Feature Enhancement (RFE) Summary: a feature to let the user "pin" (save) a specific path on AUP as a starting point when choosing assets or content links within AUP. After pinning a location, next time the user has to browse to an asset or content element, the pinned location is used as a starting point. Use-case: when editing pages on elements such as: -             content grids (articles, case studies) -             content grids (people) -             page configuration (selecting hero banner image, selecting featured image, selecting thumbnail) -             configuring links (CTA buttons, text links etc.)   Current/Experienced Behavior: Expanding the directory path from the starting point is very time consuming, an