Build better products with our product team
Comments/Updates with the most recent replies should be sorted first, and new replies should be bold or highlighted in some way. Why is this feature important to you - My users are constantly missing replies because they get lost in the threads with no obvious way to find the newest replies. Reviewers are busy people and simply will not scroll through their Updates just in case there is a reply somewhere in there. Current Behavior - Comments/Updates are sorted by their original post date & time, and all replies have the same formatting. Users must scroll down and read all the dates to see if there is anything new. With reviewers and approvers needing to look at dozens of items every day, they simply miss new replies.
Description - Currently, the % Complete status in a Program (we refer to it as a Campaign) only shows the status of projects that are in a current state. Why is this feature important to you - We want to see at a glance the status of a program/campaign and not have to sort through multiple projects to determine what project(s) may still be outstanding. How would you like the feature to work - The % Complete status would take into consideration all of the projects under the program/campaign and not just the projects in Current status. Current Behaviour -
Our users' in-app notifications are now so plentiful that they are essentially useless. It would be great if the users were able to turn selected in-app notifications "on" or "off" in their User Settings; ideally, the interface would be modeled on the one that is already in place for customizing Email Notifications. (Frankly, I was surprised to find that we can only customize the Email Notifications, and not the corresponding in-app ones...)
Our instance users are asking for a number of Subtasks to be displayed in the left navigation bar of a Parent task.This feature will prevent users missing any additional subtasks by having the number displayed similarly to how it displays the Number of Documents, and Issues.
Description - Home team and home group names should be available fields for reporting in addition to home team and group IDs. Text mode should not have to be used to create views with group and team names. Why is this feature important to you - Home team and group association are extremely important for effective reporting. Our leadership team is relying on Workfront to understand what is happening within their remits, and what teams/groups have upcoming, current, and overdue tasks. No one is able to identify what the team/group is by the ID. Reports are supposed to be clear and concise, which is why actual names should be made available instead of IDs How would you like the feature to work - Home team and group names should be available fields for all applicable reports without using text mode. Current Behaviour - Only IDs are available; no one is able to identify what the group/team is by a "random" group of letters and numbers.
Description - Create Logic for Repeating Deliveries to only send when a report's results are greater than 0Why is this feature important to you - Workers that handle multiple queues or on multiple teams would benefit from this feature so they could receive a report when infrequently queues have new requests or infrequent team task assignments come in. Report Result > 0. How would you like the feature to work - When setting up report Repeating Deliveries, have logic available to apply to a Daily delivery that it would only send if the report had >0 results. Current Behaviour - Workers that handle multiple queues or on multiple teams can be inundated by team assignment emails. Sending a Workfront report with >0 results would assist with the workers being aware of incoming work from infrequently used queues or team assignments.
Description - For those of us who find it impractical to manually manage project condition, automations like Task Tracking Mode = Auto Complete should be programmed to favor project condition rather than harm it.Why is this feature important to you - The Project Condition field can draw unnecessary ire from people who don't fully understand or appreciate what it indicates. The more we can encourage automations to help the better.How would you like the feature to work - When a task has the Task Tracking Mode set to Auto Complete, project timeline recalculation should set the task's Actual Completion Date to the task's Planned Completion Date and time so that it doesn't affect the project condition.Current Behaviour - When recalculating a project timeline, whether manually or on overnight refresh, the task's Actual Completion Date sets to the time of recalculation, which skews the project condition. Workaround: Manually update the Actual Completion Date.
In the current setup, preloading activity available in Web Application preloads the data on the basis of encrypted identifier passed in the URL parameter.It will be great to have an option to the preload the data from any selected schema and column while configuring the activity.
Many programmers and developers are eagerly awaiting the next update of JavaScript. There are many features and improvements that could be included in the next version of JavaScript, which would make programmers' lives much easier. In particular, I have been told that many programmers would be very interested in seeing more libraries included in the new version of JavaScript. This would allow programmers to have access to a wider range of functionality without having to write code from scratch. In addition, an improved code editor would also be very useful, as this would allow programmers to work more efficiently and save time. I believe that these improvements could be beneficial for all programmers, regardless of their level of experience. With the inclusion of more libraries and an improved code editor, the functionality of programs created with JavaScript would be much better, which would make for a better experience for end users. In summary, I agree that updating the version of JavaScript and including more libraries and a better code editor would be very useful for programmers and developers. This would allow for more efficient programming and better functionality, which would ultimately be beneficial for all end users.
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 where I can pull in all the tasks on a team + their PTO + their holidays + their personal assignments outside the team. On the legacy Agile places you can input capacity but it is manually put in, not automagically calculated like the WLB.
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 the livecopies.jsp (/libs/wcm/msm/components/touch-ui/livecopies/livecopies.jsp) and adding the required code but It would be great if this can be made available OOTB. Current/Experienced Behavior: RolloutDialog.html shows only page level inheritance status Improved/Expected Behavior: RolloutDialog.html should show another column to display the component level inheritance status Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service - SEP 2023 SDK Customer-name/Organization name: NA Screenshot (if applicable): By overlaying the livecopies.jsp, we can add another column and for each of the livecopy pages, we can look through all the components and see if atleast one of them has a cq:livsyncCancelled mixin added and based on that we update the status in the above table. Code package (if applicable):
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 different configuration but this is not ideal. It would mean client applications would need logic to determine when to use one Datastream ID vs another. Why is this feature important to you Use case 1: We have incoming XDM events that are specifically for Experience Platform and not Analytics. Without this feature, it's preventing us from turning on Analytics as a Datastream service. Use case 2: For privacy compliance, if a user opts out of Analytics, we should be able to prevent specific XDM events from landing into Analytics, but can be used for Event Forwarding destination. Without this feature, it's limiting the overall capability of AEP.
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 tag ~ /product/food/regional/*) - apple (select * where tag ~ /product/food/regional/apple/*) It should be made an option if the browsing has taxonomy or directory semantics. Taxonomy semantics means — narrowing down the search results to more specific categories as we walk down the branch in the tree. Imagine it like select * where tag ~/product/food* Directory semantics means displaying what is exactly associated with the tag (not with sub-tags). (select * where tag = /product/food) Many DAM systems on the market support tag-based browsing, which can be used to create multi-homed virtual directories and reduce the necessity to create live copied in DAM repos. This is a feature that would reduce a lot of headaches when migrating from a legacy DAM system to AEM Assets, See a more elaborate explanation, why this is a must-have here: https://medium.com/@achimkoch/how-not-to-migrate-asset-taxonomies-to-aem-a2f74fa203dd Use-case: Current/Experienced Behavior: Either browse for folders or filter for tags Improved/Expected Behavior: Display tags as if they were a multi-homed folder hierarchy and update the result set as you browse Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Sketch how a tag based browser could look like. Code package (if applicable):
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 AEM on the AIO side, which breaks the product scope and increases maintenance costs. Improved/Expected Behavior: Add _previewUrl to AEM CF, especially the site content Reference, and implement a specification that returns it depending on the settings. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Panasonic(PISC) Screenshot (if applicable): Code package (if applicable):
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.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
