Skip to main content

Filter by idea status

10000+ Ideas

ArthiselvaNew Participant

Enable Programmatic Extension of Content Fragment GraphQL Schema in AEMInvestigating

Request for Feature Enhancement (RFE) Summary: Enable the ability to add custom fields to the Content Fragment GraphQL schema via code, SlingDataFetcher, or programmatic means, without requiring changes to the Content Fragment Model definition in AEM. Use-case: Developers and integrators need to expose computed, derived, or integration-specific fields in the Content Fragment GraphQL API for headless delivery, without modifying the underlying Content Fragment Model. Current/Experienced Behavior: The Content Fragment GraphQL schema is auto-generated from the Content Fragment Model and system fields. It is not possible to add custom fields via code, SlingDataFetcher, or other programmatic approaches. Business Impact  Limits flexibility for headless integrations, increases maintenance overhead, and requires model changes for every new field, which may not be feasible or desirable in large organizations or for computed/integration fields. Improved/Expected Behavior: Ability to programmatically extend the Content Fragment GraphQL schema with custom fields (e.g., via SlingDataFetcher or similar mechanism), allowing dynamic, computed, or integration fields to be exposed without model changes. Environment Details (AEM version/service pack, any other specifics if applicable):   AEM 6.5 LTS; Content Fragment Models and GraphQL API; persisted queries; endpoints as described above. Customer-name/Organization name:  JPMorgan Chase Code package (if applicable): https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-expose-a-custom-resolver-field-in-content-fragments-for/m-p/776485 . I have added the code here

mmartíLevel 2

New Visualizations - Dimension HighlightNew

1) Dimension Value Highlight Visualization DescriptionIt would be great to have a new visualization in Adobe Analytics / Customer Journey Analytics that highlights dimension values. For example, showing which product has the highest conversion rate or which page is the most viewed. The visualization would be similar to a Summary Number or Summary Change, but focused on what rather than how much. Why is this feature important?Currently, summary visualizations are excellent for showcasing key metrics, but they don’t emphasize the specific dimension value driving those results. Having a way to visually highlight the top-performing dimension item would make dashboards more insightful and storytelling more effective. How would you like the feature to work?Users could select a metric and a dimension, and the visualization would automatically display the top (or bottom) dimension value according to the chosen metric. Ideally, it would also support conditional formatting (e.g., color-coding by performance) and allow display of secondary metrics for context. Current BehaviourFreeform tables are useful, but not quite visual. Additionally, there are limitations to create something a bit custom.2) Sentiment Analysis–Style VisualizationDescriptionAnother interesting visualization could be one inspired by Sentiment Analysis — designed to highlight dimension values in relation to a specific metric. It would resemble a scatter plot but use text labels instead of points, making it easier to identify and interpret key drivers at a glance. Why is this feature important?This would provide an intuitive way to analyze performance or perception differences among dimension values (e.g., campaigns, products, or pages) in a single, visually engaging chart. It’s especially useful for understanding “how each dimension feels” relative to a metric. How would you like the feature to workThe visualization could plot dimension values (as text) along two axes — for example, performance vs. volume — and apply color or font size to indicate sentiment, change, or relative importance (or even font size). Hovering over text could show detailed metrics or trends.

Extend Adobe Analytics 2.0 APIs to Support Report Suite Configuration and Processing RulesNew

DescriptionCurrently, Adobe Analytics 1.4 API provides several powerful endpoints that allow administrators to manage report suite configurations programmatically. These include the ability to:Fetch and update eVars, props, events, and classifications.Retrieve configured processing rules for a given report suite.Adobe has announced that the 1.4 API will be deprecated in favor of the 2.0 API next year. However, these configuration-level features are not yet available in the 2.0 API. Once 1.4 is removed, these critical capabilities will be lost.For many enterprise-scale implementations, this functionality is not just convenient — it is essential. Proposed ideaExtend Adobe Analytics 2.0 API to include endpoints for:Variable Management: Create, update, and fetch eVars, props, events, and classifications at the report suite level.Processing Rules: Fetch and (if possible) update processing rules for a given report suite.Cross-Suite Comparison: Provide efficient ways to compare variable configurations between report suites via API.This would ensure continuity for projects currently relying on 1.4, while aligning with the modernized API framework. Benefits / Use CasesScalability: Easily update or configure variables across multiple report suites in bulk instead of relying solely on the UI.Transparency: Retrieve all processing rules in one call, making it much easier to audit mapping when there are 100+ rules.Consistency: Compare variable configurations across report suites to ensure alignment in enterprise environments.Efficiency: Save time and reduce manual effort by automating repetitive admin tasks.Call to ActionPlease consider adding these configuration endpoints to the 2.0 API roadmap to avoid losing critical functionality when 1.4 is deprecated. This would greatly benefit customers managing multiple report suites and complex implementations.

DavidRa14
DavidRa14Level 2

Allow Versioning/Replacement of Documents in linked AEM Assets foldersNew

Description - Allow the versioning of or the replacement of documents that are in a folder in a Workfront project that is linked to AEM Assets. Why is this feature important to you -Our marketing teams use Workfront to route their materials for review and approval. There are situations where minor changes are needed to be made to documents after that are approved and moved into a folder in their Workfront project that is linked to AEM Assets. These changes are typically made by external agency partners and loaded into Workfront for review and approval routing by those agencies. Once the changes are approved, the marketers must move those changed files into the linked folder, either replacing or creating a version of what’s there. Today this functionality does not exist. The Marketer must use the following workaround:Download the document(s) from Workfront.Upload or drag/drop the document(s) into AEM Assets - they either replace what’s there or create version(s).To avoid duplicate documents, delete the document(s) from the Download location.This creates extra unnecessary steps and also creates the potential for duplicate documents if the user forgets to delete the document(s) from the download location, impacting our single source of truth.   How would you like the feature to work -The users would like to drag one or more documents (that have the same names as what’s already present in the linked folder), from one folder in their Workfront project into the project's linked folder. They should get a message, like in AEM Assets, to either replace the document(s) in the folder or create version(s).  Current Behavior - Once documents have been moved into the linked folders in a Workfront project, users are no longer able to edit, delete, replace, version, or move those documents.