Product Communities

The ability to set predecessors for issues or cross objects like tasks. Being able to set a predecessor between issues for items such as "unplanned work". Would also be nice to create cross object predecessors such as a task being a predecessor for an issue to begin.

Description -  It's great that Adobe added data visualizations to our graphs a few years ago, but the way they display isn't very visually impactful...    It's a little flag that shows in the X-Axis, leaving the users to still try to identify where exactly that point lies on the graph.     Of course, users can hover to have a line show up for the annotation.. but that doesn't really work for PDFs.. and if there are a series of annotations you can only see one at a time... let's say you are reviewing the impact of a multi-site migration rollout, you might want to see each point where sites were migrated and the impact over time of all the sites together...   Having the ability to show a permanent visual indicator would allow everyone to see at a glance where the impacts are, and users can still check the annotation details one at a time.   Why is this feature important to you - Making the annotations more visible at a glance, and being able to see mul

Description - I would like to be able to set up an email alert to notify me when specific users log in. Why is this feature important to you - This could be used to enhance the users experience of the tool.  For instance, it would be very useful to know when a new user logs in or when one of our directors/executives access to the tool - allowing us to provide better support   (I know we could technically get this information from the logs but a proactive alert would be much simpler)  

Description - The condition builder in Fusion supports a very simplistic Boolean logic, allowing simple expressions such as (A && B) || (C && D).  This is functional under many circumstances, though forces a lot of duplication of checks on the UI side. The following is an example of a condition that would be problematic: ID = "foo" && (Error 1 = true || Error 2 = true || Error 3 = true || Error 4 = true) In the existing condition builder, it results in something that looks like this: (ID = "foo" && Error 1 = true) || (ID = "foo" && Error 2 = true) || (ID = "foo" && Error 3 = true) || (ID = "foo" && Error 4 = true) If we have to change the value of "foo", this creates a risk whereby a human may miss all instances of "foo".  (This risk increases with increasingly complex conditions.) The ask is to improve the condition builder to allow for full Boolean logic.  We have a similar versi

Description -The Adobe Workfront custom API module (or any other Workfront API module) is often used to query various API endpoints.  That module doesn't appear to have any built-in mechanisms for handling a retry when a 429 (API rate limit exceeded) occurs, though this is a fairly standard and common occurrence in high-volume systems.The existing way to handle this in a reasonable fashion is to:Make the API call with the custom API moduleSet an error handler from the moduleOn the error handler path:Sleep for some amount of timeRetry the API call with a second custom API module that's configured the same way as the firstSet a success handler on that "Resumes"Set an error handler on that second moduleOn that error handler path:Do the same as on the first, and continue nesting this for as many attempts as you want/needThis is super unwieldy and means that the module configuration is duplicated or triplicated, meaning future changes need to be done multiple times, which is risky due

It would be useful, as a system admin, if an existing group could be moved into a subgroup

Description - Workfront API responses do not appear to return any kind of awareness of rate limits/available query capacity, yet will error with a HTTP 429 status code when we exceed that rate limit.  Ideally, we should know from a prior query how much capacity remains so that we can tweak any sleep calls to maximize performance. Why is this feature important to you - APIs that return 429s typically inform as to rate limits and available query capacity (example: https://www.ietf.org/archive/id/draft-ietf-httpapi-ratelimit-headers-07.html).  This allows the caller to add an appropriate sleep so as to (1) avoid the 429 error entirely and (2) minimize the delays between each call to only that which is required. How would you like the feature to work - Open to many ideas, see above. Current Behaviour - The Workfront API don't appear to return any rate limit details.

Description - Person A is editing a scenario.  Person B starts editing that same scenario. Person A saves the scenario with changes.  Person B then saves the scenario with changes. Person A's changes are lost.  Person B was unaware that Person A was (1) actively editing and (2) had saved. This is a common problem with online tools.  Some suggested solutions including (1) tracking user activity and warning other editors that someone else is ALSO looking into the file and/or (2) warning a user that someone else has saved the scenario since the scenario was opened for editing and that changes might be overwritten and/or (3) allowing an editor to "lock" the scenario for a defined amount of time so they are the only ones that can edit. Why is this feature important to you - The "simultaneous overwrite problem" is real and has forced us to have to re-do work. How would you like the feature to work - Ideally, I'd like for a simultane

Description - All objCode/search queries support $$FIRST and $$LIMIT parameters for pagination.  However, these fail to account properly for lastUpdateDate_Sort=asc where an object may be updated DURING the execution of a scenario, hence the order of entries can be changed in between each separate page query. Example: Project 1 - lastUpdateDate=1Project 2 - lastUpdateDate=2Project 3 - lastUpdateDate=3Project 4 - lastUpdateDate=4 Make a query for $$FIRST=0 $$LIMIT=2 and we get: Project 1 - lastUpdateDate=1Project 2 - lastUpdateDate=2 Then, asynchronously, let's assume that Project 2 gets updated: Project 2 - lastUpdateDate=5 Now increment the $$FIRST counter based on the prior $$LIMIT and make a query for $$FIRST=2 $$LIMIT=2 and we get: Project 4 - lastUpdateDate=4Project 2 - lastUpdateDate=5 This means Project 3 has effectively been "dropped" from the pagination. It means we have no guaranteed way to ensure that long-running p

Description - Our Adobe PS team indicated that a best practice is to create two different teams -- Production and Development -- and copy scenarios between the two teams.  Each time we do such a copy, however, we end up needing to update a variety of items, including constants.  These constants CAN be stored in variables in the scenario itself, but it forces us to constantly update the scenario for these minor value differences between the two teams. What is requested is to have a list of "global variables" (think Team-linked environment variables) that can be references using a constant reference, independent of the scenario.  The idea would be something like this: Production Environment Variable: Standard Template ID = 1234567890Development Environment Variable: Standard Template ID = 0987654321 In the Scenario:{{TeamEnvironment.`Standard Template ID`} Why is this feature important to you - We've had a number of copy-related qual

Description -Why is this feature important to you - There are multiple groups who would like to receive the notification upon data feed job completion.How would you like the feature to work - Allow "email when complete" field to except multiple emails for the data feed file completion notification.Current Behaviour - Currently, it only allows one email.

Description -  I created a new view in Setup > Schedules that includes a column for each day of the week. These are columns Workfront provides. However, there is no punctuation, so the time durations run into each other. See the screen shot attached.Why is this feature important to you - Increase legibility and understanding of the fields.How would you like the feature to work - Add a hyphen between the start and end times and a comma and space between two time ranges.Current Behaviour - There is no punctuation.

Request for Feature Enhancement (RFE) Summary: Provision to show the details of the user who triggered the last build, a tentative time estimate, and a progress bar to show the time left to deploy. Use-case: Implementing features like displaying the user who triggered the last build, a tentative time estimate, and a progress bar helps developers in various ways.   It enhances accountability, transparency, and communication among team members. Developers can better manage their time, monitor progress, troubleshoot issues (incase of longer than expected deployment). Current/Experienced Behavior: This feature is not available OOTB. Improved/Expected Behavior: Added capability to show the details of the user who triggered the last build, a tentative time estimate, and a progress bar to show the time left to deploy. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a cloud service/ AEM on-premise Customer-name/Organization nam

When working on a project timeline, there are times we may add an assignee either accidentally or the assignee is added then changed. Even when we eliminate/change the assignee name, that person remains on the project and gets email notifications as if they're still assigned. If a person is removed, they should be removed completely, not just pushed to the "Staffing/People" area.

Description - Allow Rules to be defined as to when Custom Dashboards show on Left NavigationWhy is this feature important to you - Sometimes a Dashboard that is added to a Layout Template or by a User to the Left Navigation  is only relevant for certain types of ProjectHow would you like the feature to work - Add a Rules / Filter criteria, similar to defining Typeahead fields for when the dashboard displays. Thus if I add a Dashboard to a Project on either the Layout Template or personally, allow it to only show for Projects that meet specific criteria, maybe the Portfolio is a specific one, or there is a custom field on the Project that it looks at and determines whether to display the dashboardCurrent Behaviour - Dashboard always shows up if added

Request for Feature Enhancement (RFE) Summary: Using OOTB Content Fragments multiedit resource type, all <strong> and <em> HTML tags are being replaced with <b> and <i> tags. Use-case: Using OOTB Content Fragments multiedit resource type, all <strong> and <em> HTML tags are being replaced with <b> and <i> tags. The OOTB content fragment js should have logic to retain <strong> and <em> tags and not replace them with <b> and <i> tags. This is possible in the OOTB RTE component and is an issue only with multi-edit resource type for CF. Current/Experienced Behavior: We are facing an issue with OOTB Content Fragments multiedit resource type wherein all <strong> and <em> HTML tags are being replaced with <b> and <i> tags. This is causing accessibility issues and based on our analysis, we have to override the StyledTextEditor.js file (located at /libs/dam/cfm/admin/clientlibs/v2/authoring/co

Request for Feature Enhancement (RFE) Summary: Access to detailed logs of deployment pipelines Use-case: Debugging deployment issues can be a time-consuming process, especially when faced with vague deployment logs from pipelines. This lack of clarity often leads to significant delays in issue identification and resolution, particularly in multi-module projects where pipeline runtimes can range from 1 to 1.5 hours.   Example of a vague log: Failed deployment in abc-program-dev Current/Experienced Behavior: Engaging with the support team to obtain relevant logs and resolving the issue through back-and-forth communication can be a lengthy and time-consuming process, often spanning multiple days. Improved/Expected Behavior: While it may not always be possible to obtain detailed logs for the entire deployment, it is crucial to have access to information regarding the specific cause of the failure. Environment Details (AEM version/service pack, any other specifics if appli

Request for Feature Enhancement (RFE) Summary: Flexibility to add User group as "owners" for a translation project instead of adding as single users. Use-case: We have multiple country authors who are required to be added as owners for each translation project which is a redundant activity. So having an option to add as a group will make process easier. Current/Experienced Behavior: Currently for each translation project, each users(country authors) have to be added as owners. Since every country author do not have admin access , every time a new project is created we have to add each of them as owners to make it accessible. Improved/Expected Behavior: Flexibility to add User group as owners instead of adding only single user. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a cloud service Customer-name/Organization name: Cognizant Technology solutions Screenshot (if applicable): Please find the Screenshot attached. Code packag

Request for Feature Enhancement (RFE) Summary: In a custom  ParticipantStepChooser, getParticipant()'s method return type is currently String, which means we can only return a group or a participant in the method. A provision to return multiple groups or multiple participants would be more convenient. Use-case: Custom Dynamic Participant Step Current/Experienced Behavior: ParticipantStepChooser, getParticipant()'s method return type is currently String, which means we can only return a group or a participant in the method. Improved/Expected Behavior: A provision to return multiple groups or multiple participants in getParticipant() Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: <Confidential> Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Add "Page Locked" to the List / Column view. At the moment, it seems to be available only on the Card View. Use-case: The authors would like to see if the page is locked in a Site Admin overview Current/Experienced Behavior: The "Page Locked" is only displayed as an icon in the Card View Improved/Expected Behavior: The List / Column view displays the Lock Icon for locked pages  Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.16 Touch UI Interface Customer-name/Organization name: Swisscom Screenshot (if applicable):   Code package (if applicable):  

Zusammenfassung der Funktionsverbesserungsanfrage (RFE): It is possible to go within brandportal into the admin-search-rail and edit the mimetype path for - filetypes.But it is not possible to create mimetypes a mimetype predicate folder that includes only the relevant options.Currently the mimetype within /libs/dam/options/predicates/mimetypes includes so many useless options that it is not useful. Make it possible to create a filetype search that includes only relevant filetypes. Anwendungsfall: Currently the filetype lists the following options: imagesweb -jpg-gif-png-pjpegbitmap-tiff (X)-photoshop-xcf-x-bmp-icon-bmp-ppm-pbm-pnmvector-illustrator-odg-svg-raw-dng-crw-cr2-nrwdocuments-wordpressing-word-ole2-word-ooxml-odt-pdf-html-rtf-text-docxspreadsheets-ods-excelexcel ole2excel ooxmlpresentation-odp-powerpoint-powerpoint-ole2-powerpoint-ooxml-print-indesign-postscript-pdf-quark multimediaaudio-aac-midi-3gpp-mp3-mp4-mpeg-ogg-vorbis-realaudio-wav-wmavideo-dvi-flv-mp4-m

Currently, we cannot limit access to specific folders for users. This could be a helpful security measure, as it would allow us to control who has access to sensitive data. This feature would be especially useful for organizations that onboard new users or share instance access with third parties on a regular basis. I believe that this feature would be a valuable addition to any organization's security toolkit. Thoughts are welcome! 

When a custom object record is created it is associated with a person or company record based on the link field. When that company or person is merged with another record, where the other record is the surviving one, the connection of the custom object is not carried across to the surviving record. Instead it becomes an "orphaned" record. It would be wildly helpful to be able to carry this association across in a merge. There are other scenarios too where it can be extremely unhelpful that custom object records cannot be corrected to associate with a different record after creation.

It's great that users can log time in WF via the Creative Cloud WF plugin. However, some of our teams are pretty strict on adding notes when logging time, and this is not currently available in the plugin, so it is an obstacle to get some teams to use this. Thanks for considering!

Description - Add Updates to Boards for commenting similar to functionality in Microsoft Planner Why is this feature important to you - Comments made on the project progress could be date/time stamped   How would you like the feature to work - Similar to other objects in Workfront, Boards would have Updates Current Behaviour - Boards do not have Updates