Adobe Workfront

Description - Currently, when printing a dashboard directly from the platform, the print view does not automatically adjust to align properly. Although manual adjustments are available on our end to ensure proper alignment in the print preview, the process is not dynamic and requires user intervention.Request: We would like to request the ability for the print view of dashboards to dynamically adjust to ensure proper alignment, without requiring any manual adjustments from the user. This would provide a smoother, more seamless experience for users who frequently print dashboards and improve overall usability. Why is this feature important to you - Eliminates the need for manual intervention each time a dashboard is printed.Enhances user experience by ensuring that all elements on the dashboard are properly aligned in the print preview, making it more efficient for users.Streamlines the process for those who rely on printed reports for presentations or documentation.

Description:There is a critical inconsistency between the activity records in the Adobe Admin Console and the logs shown in Workfront. When users make changes — such as editing profiles or managing access — via the Admin Console, these actions are not properly attributed in Workfront logs.Why is this feature important to you:Accurate traceability is essential for our security, audit, and compliance processes. Without clear identification of the user who performed a change, we face risks in governance and accountability. This is especially critical during permission reviews, account deactivations, or investigations.How would you like the feature to work:Workfront should reflect the actual user who performed the action in the Admin Console, both in the system logs and in Journal reports. Instead of showing “System” or generic labels, the logs should capture and display the authenticated user responsible for the change.Current Behaviour:Changes made in the Admin Console appear in Workfron

Description - Support WebP image file format for document upload and sharing (Not needed for proofing purposes)  Why is this feature important to you - My team manages our corporate websites - those sites primarily use WebP file formatted images for page load speed and other reasons as supported by industry best practices.  As an enterprise we use Workfront for request and project intake - so someone from another group within the enterprise can send a Workfront request to my team to update/create a web page - this included updating images - those individuals need to have the ability to upload and share WebP files with my team via Workfront for us to load to our DAM and websites. We would not need the ability to create WF proofs of these images.  How would you like the feature to work - simply upload WebP file formatted images to documents within Projects and/or intake requests - again, for sharing purposes, not needed for proofing. Current Behavior - WebP

Description - Any validation possibilites for entered values into custom fields would be great. Why is this feature important to you - At the moment there is no possibility to validate any entered values into fields. We cannot validate, if e.g. a valid email address, or url was entered, also for date fields it is not possible to define, e.g. that the allowed choices have to be after a specific date,... How would you like the feature to work - RegEx would be fine Current Behaviour - no validation

We should be able to reference custom fields associated to a Typeahead object through Calculated Custom Fields and Calculated Columns.valuefield=[Typeahead Field Name]:[Custom Field]Ex. My organization uses a User Custom Form to track employee details such as 'Department' or 'Employee Number'. When a request is submitted on behalf of another employee we would like to use the Typeahead field to identify the employee and then have a set of calculated custom fields to 'auto fill' in the rest of the employee details.

We have roughly 7,500+ users on Workfront globally.In a small number of cases, where a user shares the same first name and last name, we are unable to distinguish which user is which when "@" tagging them into an update or other.It would be great if Workfront could either add an additional data point when tagging users in updates or add the user profile hover-over functionality to the draft update module to help determine if you are reaching the right person.Example below:Any questions, do let me know.Best regards,Christian

Description - We currently are using typeahead fields for single select employee lists on a custom form for Marketing and have a need to have an employee list with a multi-select optionWhy is this feature important to you - Since employee data lives in Workfront, it makes sense to be able to choose the appropriate information from Workfront instead of having to point to an external resourceHow would you like the feature to work - Would like the Typeahead field to be able to have both a single select and multi-select optionCurrent Behaviour - Typeahead field only allows a single select option

We are creating a photography brief in a custom form, and it would be helpful if each checkbox included the photo angle name along with a reference image

Description -  In the Priorities module, we would like an option for the bars on the calendar view to span the duration of the task based on the planned start and planned completion dates? Why is this feature important to you -  Allows users to see how busy they are each day on the calendar Current Behaviour -Currently, the bars only show based on single date; the planned completion date

We have a mismatch between the [Priority] field values when creating a project from an issue using a template. Use case: We have an issue with a high priority. When we convert it to a project, the new project has a medium priority. We want the project to reflect the original project's priority. The cause: The Project Template requires a [Priority] value. All projects created using that template will have that value, regardless of the original request's priority. Proposal: When creating projects using a template, the new project inherits the [Priority] value from the original request. (Or have the ability to leave the Template value blank, so people who want items with that template to always have the same priority can have that option too) Benefits: Workfront user does not have to manually change the project Priority to match.When creating projects, other Project fields inherit values from the original request. Having [Priority] inherit values would lead to a consistent use

Description - The Delegate feature should include all the options like assignments, access to campaigns, email notifications/updates,etc and should not only limit to approvals.Why is this feature important to you - We have set up assignments for group leads who if go on vacations, we have to manually change the assignments for that period to anyone who is covering up for them. Also when they are back, it needs to be assigned back to group leaders. This is done on routers on queu topics or through fusion scenarios in some cases where we need to update everytime. If this can be covered under delegations, it would be great.How would you like the feature to work - It should automatically pick any assignments/notifictaion/ownership of campaigns to be asisgned to the delegated user.Current Behaviour - It only works for approvals, not for assignments and updates and project ownership.

It would be very helpful if approval paths could vary based on selections made in a Request Queue form request. Currently, when the issue request is submitted, it follows the one, pre-defined approval path. What we are looking for a way to have different approval paths that get triggered by a selection on the request. For example, the requestor selects between two radial buttons, A or B. Depending on which one is selected, the approval path is different.