Product ideas | Community
Skip to main content

Ideas

Filter by idea status

10000+ Ideas

ManjunathaGNew Member

Enable Hyperlinked Project Names in Team Request widgetNew

Description - The project name is no longer a link that will allow me to look at the project before assigning it to someone. That is something that used to be there, but went away with this recent fix.Why is this feature important to you - This feature is important because having the project name as a clickable hyperlink in the widget allowed us to quickly access project details before assigning tasks. It helped ensure we had the right context and reduced the chances of misassignments. Removing this functionality adds extra steps to our workflow and impacts efficiency, especially when managing a high volume of requests. Restoring it would significantly improve usability and productivity.How would you like the feature to work - We would like the project name in the widget to function as a clickable hyperlink, similar to how the task name works currently. Clicking the project name should open the project in a new tab or window, allowing us to quickly view its details without navigating away from the current page. This would help streamline our workflow by providing immediate access to relevant project information before making assignment decisions.Current Behaviour - In the current setup, only the task name appears as a clickable hyperlink in the widget. The project name is displayed as plain text and is no longer a link. As a result, users are unable to directly access the project from the widget, which limits their ability to quickly review project details before assigning tasks.

Workfront External Lookup – Retrieve/Send Workfront Record ID & Details in WebhookNew

Description -When using external lookup fields in Workfront (e.g., dropdowns that fetch values from external systems via webhook), there's currently no way to know which Workfront object or record the user is editing or interacting with when the webhook call is triggered. This limitation hinders the ability to tailor results or logic based on the specific context of the Workfront record, such as a project, task, or custom form.Why is this feature important to you - As an integration architect working extensively with Workfront Fusion and other middleware platforms, we frequently design experiences where dynamic dropdowns should return context-aware results. For example, showing different vendor lists, funding sources, or templates based on the portfolio, project type, or requestor. Without knowing which Workfront record the user is interacting with, we are forced to build complex workarounds, cache lookups, or create duplicative forms, all of which introduce fragility and increase cost and implementation time. This change would enable smarter, more responsive external lookups and unlock a wide range of enterprise use cases.How would you like the feature to work - When a user interacts with an external lookup field and the webhook is triggered, Workfront should include the context of the record (e.g., record ID, object type, or other related metadata) in either the HTTP headers or the body payload of the webhook request. Ideally, this would be configurable so admins can choose to send fields like projectID, customFormID, or even specific custom field values (e.g., selected portfolio or request type) to allow for contextual logic in the receiving system or Fusion scenario.Current Behaviour - Currently, Workfront external lookup webhooks send no identifying information about the record or object the field is on. This results in a "blind" call to the external system with no context, preventing the use of record-specific logic, filtering, or validation in the external lookup response.

[Content Hub] Enable Public Share Links for CollectionsNew

Request for Feature Enhancement (RFE) Summary: Enable public share links for Collections in Content Hub, allowing dynamic updates to be reflected in the shared content. Use-case: Our client frequently shares Collections externally, including in press releases and with large audiences. They need a stable, public share link that reflects real-time changes to the Collection (e.g., adding or removing assets). This ensures consistency and avoids confusion or reputational risk. Current/Experienced Behavior: Currently, Adobe recommends selecting all assets within a Collection and sharing them via the Share Link feature. However, this link is static: any changes made to the Collection afterward (such as adding or removing assets) are not reflected in the shared link. To update the content, a new link must be generated and redistributed. Improved/Expected Behavior: Collections should be directly shareable via a public link. This link should always reflect the current state of the Collection, including any modifications made after the link was created. This would eliminate the need to regenerate and redistribute links, which is not feasible when links are widely shared or embedded in press releases. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets as a Cloud Service - Content Hub Customer-name/Organization name: Audemars Piguet (client) / Valtech (integration partner) Screenshot (if applicable):   Code package (if applicable):  

[Content Hub] Add a "Shared Links" interface with enhanced link management capabilitiesNew

Request for Feature Enhancement (RFE) Summary: Add a "Shared Links" interface in Content Hub with enhanced link management capabilities. Use-case: Users need a centralized interface to manage all their public shared links within Content Hub. This includes editing, reactivating, and searching links, as well as setting default expiration rules. These features are essential for maintaining control over public asset distribution and improving collaboration. Current/Experienced Behavior: Currently, Content Hub does not provide a dedicated interface for managing shared links (Private and Public). Users cannot view or edit their previously generated links, nor can they see links shared by others. There is no way to search/filter shared links, reactivate expired ones, or set a default expiration period. Improved/Expected Behavior: A dedicated "Shared Links" interface accessible from the Content Hub UI. At least for public shared links. Users can: Edit their own shared links (e.g., change expiration date). Reactivate expired links. View links shared by other users (with appropriate permissions). Search and filter shared links by asset name, user, date, etc. Set a custom default expiration date for public links (e.g., 1 year). Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets as a Cloud Service : Content Hub Customer-name/Organization name: Client : Audemars Piguet / Integrator : Valtech Screenshot (if applicable):   Code package (if applicable):  

MandyGeorge
Community Advisor and Adobe Champion
MandyGeorgeCommunity Advisor and Adobe Champion

Trending summary row in line/area chart produces incorrect values when only part of a dimension is in a tableNew

Description - When building a freeform table with a subset of a dimension (either using a filter, using display only selected rows, or dropping individual dimension items), if you try to make a line/area visualization that is trended over time from the summary row it uses the entire dimension and not just the items that you've dragged in. This is a problem because it isn't accurately trending the dimension items that you have selected, it is including information that is not in the table and leads to an inaccurate representation. You can see here, with the header/summary row selected, it's trending the entire dimension, because the total for some of the single days in the line graph is greater than the total for the two weeks in the table.    Why is this feature important to you - This feature is important because when building out trended visualizations, we rely on having accurate information displayed. There are times that we need to trend the sum of a couple items from a dimension, and in some cases using a segment won't work because there is no sub-hit filtering (this is especially important when using product related dimensions). This limits our ability to create useful visualizations within workspace.   How would you like the feature to work - When selecting the summary row (or any row), the associated line/area visualization should display the trended number from the selected row only. If only part of a dimension is in the table (either from a filter or dropping individual dimension items), the visualization should only include data from those items so that the graph matches what is in the freeform table.    Current Behaviour - Currently when selecting the summary row, it is trending the entire dimension regardless of how many items are displayed in the table.