Product ideas | Community
Skip to main content

Ideas

Filter by idea status

10000+ Ideas

HamzaBE2New Member

Support for Custom Field Types in Cloud Manager Content Fragment EditorInvestigating

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, making values stored in these fields inaccessible. Users must use the classic editor to maintain content integrity, reducing the adoption of the new UI. Expected Behavior: Support for rendering custom field types within the new CF Editor. The ability to register and reference custom client-side renderers for field visualization. Improved UI extensibility to maintain parity with the classic editor’s capabilities. Steps to Reproduce: Replace a single-line text field with a ColorField, TextArea, or PathField. Open the Content Fragment in the new CF Editor. Observe that the field does not render as expected. Open the same fragment in the classic editor and see the expected rendering. Impact & Benefits: Ensures a seamless transition from the classic editor to the new UI. Improves content authoring experience by maintaining structured field visualizations. Encourages adoption of the new CF Editor without sacrificing customization. We appreciate Adobe’s continued improvements and request consideration for this enhancement in a future release. Thank you for reviewing this proposal.  

Request to improve the way we choose folders for pages or assets by saving the folder choice for later use.Investigating

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, and it needs to be done multiple times -             Country branches are not sorted in a meaningful way, which makes it very difficult to find the needed folder in the directory tree Improved/Expected Behavior: Example scenario 1 (non-exhaustive of the use cases): In a content grid, the user clicks to add a new item. They click the folder icon which opens the content structure starting at the "EY Unified Site" level. The user finds the directory which they want to be the new starting point for adding content to content grids and they "pin" and save this directory location.   Once this is enhanced, in content grid, when clicking the folder icon, it starts browsing from the saved (pinned) location. The user has the option to unpin the folder and pin a new one if needed. Example scenario 2 (non-exhaustive of the use cases): Similar thing happens in the Page Properties / Images tab, where the user defines the assets to be used as page thumbnail and featured image. The "Pick" and "Select image" links open a dialog window which starts at the pinned location for assets.   Note : the pinned locations for assets and for content are different. The user can pin a location for each of the different use cases – for content fragments, for links, for images and for documents Environment Details (AEM version/service pack, any other specifics if applicable): 2025.1.19149.20250116T154450Z Customer-name/Organization name: Aneesh.KM@gds.ey.com / Hans.vinje@nl.ey.com / EY / EY.COM Screenshot (if applicable): NA Code package (if applicable): NA

Layout Templates Dynamic based on Object ContextNew

Issue -The Layout Templates are a great way to tailor the user experience in the system.   However, we use the system at an enterprise level with various tenants using the system using the Group setup.  The problem is we have users that work with multiple groups in the system.   The layout template assigned to them as part of their home group may not align when they are working on work objects from another group. For example, a User 1 in Group A may hide Business Case section of a project to meet their operational needs.   However, User 1 may have to work on a project that is managed by Group B that uses Business Case.  Because User 1's layout template hides Business Case, they cannot see the Business Case section in Group B's project. How would you like the feature to work -I would like layout templates differentiate between overall/default view of the system, and the context of the object they are looking at (portfolio, program, project, task, issue, team, etc.).  This would probably involve defining the layout template at the group level so that all objects for that group inherit the layout. For example, if a user is part of Group A with a specific layout template that does not show Business Case, but they are viewing a Project that is linked to Group B where that group's layout template shows Business Case, then show the Business Case section.

Ability to create segments based on rolling current timestamp with BEFORE and AFTER clause in Audience Builder UINew

Description -Why is this feature important to you - In. last 3/4 years of working with various use cases I have delt with, a very common use case I came across is creating segment using some date field where the audience building criteria is:date is before current timestampdate is after current timestamp For last 3/4 years, I have been handling this type of requests/requirementsusing data distiller Query Service Only ORhave an additional field "status" and requesting data source to derive and set the value or adding computed field mapping in the dataflow during ingestion  All these options create an additional complexity. As users of AEP is mainly expected to be marketers, I think for this type of simple use cases, reaching out to IT team pushes the capability AEP in bad place - I have seen people raising eyebrows.  There are so many features getting added in AEP every month. Can't we expect an enhancement in AEP Audience Builder UI to be able to do this using Audience Builder UI only? This will make it more powerful to position. With the existing capability of AEP, I am able to create the segment with the above criteria using PQL and API. But enabling the Current Timestamp as TIME option after the DIRECTION (BEFORE and AFTER) would be a great enhancement for AEP.   How would you like the feature to work - Bring the Current Timestamp option after the DIRECTION (BEFORE and AFTER) in the Audience Builder UI.Current Behaviour - Currently there is no option in Audience Builder UI to select current timestamp when we select "BEFORE" or "AFTER" for a date/datetime field. Note: A question was raised and we discussed about the existing capability in this URL: https://experienceleaguecommunities.adobe.com/t5/real-time-customer-data-platform/create-audience-where-profiles-having-an-active-subscription/m-p/730786?search=Audience%20Builder%20-%20RT-CDP#M1223 @davidross91 @pratheeparunraj