Product Communities

It would be great to see an audit trail on who created and/or edited a Group or Team - audit trail would include the user name, date, and time (eg. Created by Xuser on date/time and Edited by Xuser on date/time). This would be helpful for when we are managing the ongoing maintenance/audits of our system as well as in the chance something was changed by accident or by error. It would be good to know who to reach out to about the Group/Team that was edited.

Description - Collapsing messages in WF projects/tasksWhy is this feature important to you - It prevents you from having to read through strings of messages when they have been addressed and don't need to be looked at again. Unnecessary clutter in the space.How would you like the feature to work - Ability to collapse messages in specific tasks.Current Behaviour - Seeing the long list of back-and-forth communication.

It would be awesome to be able to set a sort on the grouping of a report. Currently the grouping is set and displays in a random sort. Our company would love to be able to set a sort for the grouping so things always come in in alphabetical order.

Description - If possible, allow for the download of a single PDF of all current WF documentation. We can only view documentation online, and the new format is really challenging to manually navigate since everything is collapsed and hidden. Have to hit View More constantly to see all the different areas. Having documentation could also allow for easier searches since online search results aren't always the easiest to navigate. It could open the possibility for AI options as well since Adobe hasn't shown any advancements there to make it easy to have a conversation with a PDF to find the answers you are looking for. Thanks! Why is this feature important to you - Easier access, AI advancements How would you like the feature to work - Easily found link to download all documentation as an organized PDF.  Current Behaviour - Have to view it online, and I personally hate the new format with everything hidden behind View more links. 

Description -The Workload Balancer is AMAZING for individual users, but I would love to see a version where I could see a full team as a line on the WLB. For Agile teams who self assign/claim work, we'd like to be able to compare how much work is outstanding for the team vs how much availability they have that week to complete the work.  Why is this feature important to you -Knowing lead times for teams, capacity planning if one team is getting overloaded or not.  How would you like the feature to work -I'd love to be able to set the capacity of any given team as a static number like you do for an individual user. That team would appear as a line item on the WLB with the "available" time pulling in based on their static capacity minus holidays. Then it would pull in all the work assigned to that team, as well as all the work assigned to the users of that team AND the PTO of users on that team. Current Behavior -Currently there is not one place in Workfront wher

Request for Feature Enhancement (RFE) Summary: DataDog integration for report monitoring tools. Use-case: Most organizations now are using DataDog for monitoring systems.  Current/Experienced Behavior: Currently, AEM can only be integrated with Splunk.  Improved/Expected Behavior: Able to comply with different company standards especially for organizations that are using DataDog and not Splunk Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: Proquire Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: GraphQL API to get References to a Content Fragment/Asset Use-case: In a headless approach utilizing GraphQL with content fragments, we aim to clear the cache on a third-party app whenever content is manually updated on AEM or via packages. Additionally, we seek to reset the cache for other content that references the updated content fragment or asset. Current/Experienced Behavior: We are unable to find the content referencing the updated CF/asset via GraphQL queries. Improved/Expected Behavior: Should be able to find the content referencing the updated CF/asset via GraphQL queries. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Description -Why is this feature important to you - We've had deleted timesheets and unsure who/how it was done. How would you like the feature to work - Ability to audit who and when the timesheet was deleted. Current Behaviour - Can only edit hour deletion not hour deletion.

Request for Feature Enhancement (RFE) Summary: Enable Component level inheritance status OOTB without the need to overlay  Use-case: As a content author, MSM roll-outs is a key content authoring activity. When a content author performs a roll-out of the content from the language master to the related livecopies, there is a provision to see the page level inheritance status in the rolloutdialog.html. But this page doesn't provide any information about the component level inheritance status of all the components inside the live-copy page. At times, this creates a lot of confusion where a content author is trying to roll-out a page to live copy but some components are not getting updated due to the fact that component inheritance is broken on the live-copy page. if there are too many components on the page, then it becomes very tedious process for the content author to check each and  every component for its inheritance status. Currently, this can be solved by overlaying t

Currently when receiving reminder notification the email received is static and doesn't actually link to the project or task being referenced. This causes confusion because tasks can have the same name under different projects. (e.g., copyediting, etc.) I'd like to suggest a "See it in Workfront" link be added to each reminder email to make it easier and more efficient to link to the item from the reminder.

Description There needs to be a way for incoming XDM events to be filtered/routed to specific enabled Datastream Service.   Current Behaviour Currently when we enable Analytics, Experience Platform, Event Forwarding for example, all incoming XDM events are pushed to all the enabled Services for the give Datastream ID. There needs to be a way to selectively choose which XDM events should be accepted by the enabled Services.    How would you like the feature to workCurrently, we can do this for Event Forwarding using Rules, so that we can selectively decide what XDM events needs to be forwarded to a 3rd party destination. We need a similar setup for the other Datastream services. Not every incoming XDM event is relevant to Analytics or Experience Platform. We don't want for example Analytics to be incrementing Occurrences for XDM events that are meant for Experience Platform or Event Forwarding.    One possible workaround is to operate multiple Datastreams with d

Request for Feature Enhancement (RFE) Summary: AEM Assets supports   browsing through folders and form-based searching for tags Other DAM systems offer a third alternative:  tag-based browsing In these systems the tag hierarchy would be rendered as if it was a folder and users can naturally browse through the folders. Whenever you'd "browse" to the next tag, the UI would display the assets tagged with these current tag.    Yes - in principle AEM supports that case already: You can  a) Open the filter b) Click on a tag filter c) Browse to the tag you want to search for d) Select that tag e) Submit the search form.   "Real" tag based browsing is a one-step interaction, only. You would "open" a tag from the "hierarchy" side rail - and AEM would implicitly display all assets with that tag. Imagine it as implicit search-as-you browse: product (select * where tag ~ /product/*) - food (select * where tag ~ /product/food/*) - regional (select * where t

Request for Feature Enhancement (RFE) Summary: ▽ Product-side collection response (request)Add _previewUrl to AEM CF, especially the site content Reference, and implement a specification that returns it depending on the settings. Use-case:   Current/Experienced Behavior: ▽ BackgroundIn normal page rendering, AEM constructs a URL for the set path, including resource mapping and domain settings, and returns it to the front end.These are the same for CF graphQL, and you can get information resolved from the path.Example) Set the site path in CF → CF graphQL returns the full URL of author and publish in a specific json format ▽ ChallengesThe particular json above is called Reference, but there is no previewURL present inside the Reference for the path to the site content_authorUrl: Exists_publishUrl : Exists_previewUrl : does not existTherefore, in order to set the preview URL, it becomes necessary to configure, manage, and implement resource mapping, domains, rules, etc. on A

Request for Feature Enhancement (RFE) Summary: When setting the page property "(Example) Redirect" for a launch page with the URL in the launch and promoting the launch, it is not reflected in the page property "Redirect" of the original source. Use-case: I want to change the redirect property for the launch page and have it reflected on the source page when promoted. Current/Experienced Behavior: In addition to redirect properties, title and description properties were also not reflected during promotion. Improved/Expected Behavior: I would also like page properties to be reflected as a parameter when promoted. Environment Details (AEM version/service pack, any other specifics if applicable): 2023.10.13804.20231005T183332Z Customer-name/Organization name: Panasonic　（IBM　Digital　Service） Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Mindmap view for a CF hierarchy Use-case: The Mindmap view for a hierarchy of CF. It will make it easy to browse and Edit the CF down the hierarchy. Current/Experienced Behavior: Authors need to manually browse to the CF. And if the CF is linked to futher CF, it becomes more difficult to browse and reach. Improved/Expected Behavior: Authors would easily be able to reach and edit a linked CF. Environment Details (AEM version/service pack, any other specifics if applicable): Authors would easily be able to reach and edit a linked CF. Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Provide a way to edit and repurpose a completed DW request instead of duplicating it.Sometimes, a "completed" Data warehouse request can be repurposed to extract the same data again. When such requirements arise, the current design does not allow us to "edit" a completed data warehouse request providing a quick way to run them for a different date range, instead it requires one to duplicate the DW request and create a new one out of it.To me, this results in:1. Duplication of DW requests whenever similar "one time" extraction needs arise. 2. Increases the list of dormant "completed DW requests", thus clustering the DW request queue.3. Time & effort is spent in recreating the same request again - this can be avoided.Provide edit feature to improve user experience. Duplication can be used where necessary.

Provide an Workflow mechanism to update fields, send email notifications and create tasks based on admin defined criteria.

We have many use cases where a template in Workfront (Template to create a new Project with assigned tasks). So that a task being created - can be assigned to the user via option like -- $$USER.ID Example we have 50+ people in one of our teams that each has their own Template. All templates are identical except for about 15 tasks that they needs to be assigned to. It would make sense to have a single template - as currently we have to update these about every 2 months. And bulk updating doesn't work.

With the new Terminology feature for Layout Templates, it would be nice if we could change a term to a term that is spelled with all capital letters. For example our group wants to change the term Issue to RAID. Currently Workfront will only allows the first letter of the new term to be capitalized, such as Raid.

We need the ability to control the inherited document permissions at the project/task/request level. Currently there is only the ability to "never inherit document access from projects, tasks, requests, etc." within an Access Level. Since this is an all or none setting, we have to manually adjust sharing on each document and would like to control document permissions at various other levels.

Allow For creation of API only Users with granlar access rights for integrations with 3 rd party systems, without needing to grant them Sys Admin Access or UI access

Request for Feature Enhancement (RFE) Summary: Currently when you use Manage Publication functionality to publish/unpublish pages, the timeline does NOT provide information about the target so that you can not see to which target it was published/unpublished. And instead of "Page published" entry like in AEM 6.5.16 on Prem only workflow steps are visible which is confusing. Use-case: Timeline should give the possibility the see what happened to page and it is important to know which target was published. If you have pages which are frequently published a clear overview is needed of editors. Current/Experienced Behavior: Missing information about publishing target. Listing of workflow steps for publication which are confusing. Improved/Expected Behavior: Provide proper information about the target to which the page has been published to. Use clear entries for publication like "Page published to Publish" or "Page published to Preview" instead of listing connected workflow steps

Request for Feature Enhancement (RFE) Summary: Open "Reveal in Sites" and "Reveal in Assets" links in the new browser tab automatically Use-case: AEM author users needs to open several Page's or Asset's language copies at the same time, so that they can compare the content on different locales. Current/Experienced Behavior: "Reveal in Sites" link is not opened in the new browser Tab even automatically. "Reveal in Sites" link is not opened in the new browser Tab even if I press "cntrl" key on the keyboard. Improved/Expected Behavior: "Reveal in Sites" link is always opened in the new browser Tab even (without pressing "cntrl" key on the keyboard). Environment Details (AEM version/service pack, any other specifics if applicable): Tested on the clean AEM 6.5.19 (without our application) Oracle JDK 11.0.20 Customer-name/Organization name: Veeam Software Screenshot (if applicable): Click on the Page or Asset Go to the "References", then "Language copies" Select a langua

Request for Feature Enhancement (RFE) Summary: Enhancement request to add 2 uicontrol elements when a menuscascase is inserted, instead of one. Use-case: Insert menucascade then insert another uicontrol to achive the end goal. Current/Experienced Behavior: When a menucascade is inserted, a single uicontrol is added. Improved/Expected Behavior: When a manucascade is inserted, 2 uicontrols are added. At the preview output, a caret is placed between the two uicontrols. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.18SP, AEM Guides 4.3 Customer-name/Organization name: Olu Oladipo / Verizon Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: From Guides, add an option to open dita topics and maps in Source view. Use-case: Navigate to a dita topic or map in Guides; click Options; select 'Edit Source' or 'Check out in Source'. Current/Experienced Behavior: Dita topics and maps are opened in Author view. Improved/Expected Behavior: Provide an option to open dita topics and maps in Source view. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.18,  AEM Guides 4.3 Customer-name/Organization name: Olu Oladipo / Verizon Screenshot (if applicable):   Code package (if applicable):