We're currently undergoing an exercise to fully automate our reporting. We have a number of scheduled reports (report builder) and projects (analysis workspace) that need to go external to our company, and as per company policy, I need to be password protect them before they can be sent.Would it be possible to introduce as system that would allow us to apply password protection to files as part of the scheduling tools?
In design studio, we are able to move image or file from one folder to another folder. It would be great that we can move Advanced BI Analytics reports from one folder to another folder. This will be very helpful to re-organize the reports location. Right now, we cannot move the reports from one folder to another. Thanks
Description - Rich text fields have a few oddities when they are used in an External Lookup Field interaction. Rich text fields can cause External lookup fields to fail to be able to be selected OR result in an output that is not user-friendly. Why is this feature important to you - The more consistent a feature is in Workfront, the more likely it is that I can use it to design a useful and impactful UX for my team. How would you like the feature to work - Either bring in full support for user-friendly Rich Text results in External lookup fields, or give additional features in the setup of an External Lookup Field to allow for system admins to control the results of the field. Current Behaviour - 1. The 2,000 character limit on an external lookup field will run into a conflict pretty easily when returning the results of a rich text field which to my understanding has a 15,000 character limit. The results of a rich text field are returned with their JSON wrapper intact. This uses quite a few characters, especially in results with multiple paragraphs or a good deal of "rich text" like attributes. It also displays the JSON wrapped output to a user which can be extremely confusing. Additionally, a calculated field, or a block of textmode akin must be used to "Clean up" the result. Example here:valueexpression=IF(CONTAINS("text",{DE:YOUR CUSTOM FIELD}), LEFT(SUBSTR({DE:YOUR CUSTOM FIELD},SUM(SEARCH("text",{DE:YOUR CUSTOM FIELD},1),7),LEN({DE:YOUR CUSTOM FIELD})), SUM(SEARCH("type",SUBSTR({DE:YOUR CUSTOM FIELD},SUM(SEARCH("text",{DE:YOUR CUSTOM FIELD},1),7),LEN({DE:YOUR CUSTOM FIELD})),1),-3)),"") 2. Manipulating a field with a dependency can cause an error result on an otherwise valid choice, creating hidden "invalid" choice amongst valid choices all driven by character limits. This is difficult to control because the JSON wrapper is variable as well, so text block of 1,800 characters could be valid in some cases and invalid in others solely based on how many paragraphs were used in the text. 3. There seems to be no support for a JSON Path-based "cleaning" of the output of an external lookup field.Example:$.data[*].parameterValues['DE:YOUR CUSTOM FIELD'] ---> This one works, but results in the JSON wrapped text$.data[*].parameterValues['DE:YOUR CUSTOM FIELD'].blocks[*].text ---> Does not work$.data[*].parameterValues['DE:YOUR CUSTOM FIELD'].blocks[0].text ----> Does not workIf either of the 2nd or 3rd approaches worked, we could bypass some of the obscure and inconsistent outputs we get as of today by trimming the results of their JSON wrappers.
Description - Allow lookup field results to serve as the basis for display logic within a custom form. (Especially $$HOST-based fields) Why is this feature important to you - This would bring external lookup fields to parity with other selection-driven logic on other field types in Workfront. How would you like the feature to work - When a user makes a selection in an external lookup field, that field should be added to the list of possible display-logic and skip-logic choices in subsequent fields within the same custom form. Just as dropdown fields do today. This allows for greater control and intelligence within a custom form design process to ensure users are guided to selections that make sense for a particular end-goal. Current Behaviour - External lookup fields are not recognized by the system as valid choice for which a user can initiate display or skip logic.
Description - When using a $$HOST-based external lookup field and maintaining a data table, such as a list of US States, users currently have to click on each valid option that appears in the picklist for a multi-select-allowed External lookup field. Why is this feature important to you - This will bring parity to the External Lookup Field with the Multi-select Dropdown field. Much of the discussion around external lookup fields is that they can be used as a dependency-driven list of results that helps control front-end user input, especially when flowing through a custom form for an intake process. This really supports staying away from the "Garbage in, garbage out" trap of users mis-selecting options in an intake process. How would you like the feature to work - When "Multi Select Dropdown" is selected in the field setup, users should be given a UI-button that responds the same way the current Multi-select options (Dropdown, Checkboxes) works. A "Select All" option should populate all of the choices that are valid for the JSON path, and then from there, users should be able to use the "x" button on the individual choices they DO NOT want to include. When the 1st option removed, the "Select All" button should also clear, allowing for it to be re-selected, and any options that were removed, should be re-added to the list within the field. Current Behaviour - Users have to click every valid option in an external lookup field result. Bonus fix/Observation!!! - The user experience when selecting multiple options from an external lookup seems to be wildly inconsistent. Some users can click a result, and the list of possible results stays open allowing them to quickly click more options to add to the selection. Other users have the external lookup dropdown interface close with each and every selection, requiring an additional click to re-open the selection field, and another click to select an item, which subsequently closes the field again.
We would like the Workfront Mobile App to allow the screen to be mobile-responsive and display all information in landscape mode.Some of our project names are long so it only displays some of first and last characters with an ellipsis in the middle when searching for projects. We are hoping landscape mode would fix that issue and make the app more user friendly.
Description - Do not allow time to be entered on a project or task before the Start Date (planned or actual) Why is this feature important to you - better compliance when it comes to entering time/timesheets and in the end give more accurate reporting. Currently our team is using Workfront for time/timesheets so it is important to be as accurate as possible. How would you like the feature to work - When a user goes to enter time on a project or task, the days before the start date of the object are greyed out, not allowing them to enter time in the past or before the object was created. Helpful if this could be an option in the Setup menu. Current Behavior - The user can enter time in the past for a project or task that was just created, giving inaccurate data on Timesheets and in reporting.
When a user is deactivated, they should be removed everywhere. I keep finding little easter eggs of old users and can't even begin to find all the places they need to be removed. Examples, assignments on templates, sharing on projects created from templates, custom views sharing. The only thing that should remain, is a history of what they did. They should not still have views and such shared with them or newly created projects shared/assigned.
Description Sorting for bucketed dimensions in CJA should default to logical sorting by the dimension's numerical value, rather than it's label. Buckets should be displayed more clearly (Less than 30, 30 to 59, 60 to 119, 120 or more) Why is this feature important to you Bucketed dimensions are intuitively understood when sorted in logical order by the value of the dimension. For example, shortest to longest time. It's confusing when two buckets are ambiguously defined and contain the same value (example: 30 to 60, 60 to 120). How would you like the feature to work Bucketed dimensions should default to logical sorting by the dimensions numerical value. At a minimum, users should have the option to sort by logical order. Example: If I have a bucketed dimension for time in seconds (Less than 30, 30-60, 60-120, 120 or more), I'd like the option to sort them logically as either: Less than 30, 30 to 60, 60 to 120, 120 or more, or 120 or more, 60 to 120, 30 to 60, Less than 30 Bucket ranges should be clearly displayed (without any overlap) Current Behavior Sorting by the bucketed dimension sorts by non-intuitive, alpha-numeric orders either: Less than 30, 60 to 120, 30 to 60, 120 or more, or 120 or more, 30 to 60, 60 to 120, Less than 30 Bucket ranges overlap (30 to 60, 60 to 120, 120 or more), causing confusion.
Why is this feature important to you - Everyone has done it: Deleted a report when they didn't mean to or know better. This moves cheese for our users and creates more admin work. How would you like the feature to work - Like other objects, send deleted reports to the recycle bin and therefore allow admins to restore them. Current Behaviour - We cannot restore reports. They're gone forever upon delete.
If you delete a project it is permanent. Adobe should implement a 30 day recycle bin where you can restore your deleted projects.
It would be great if we can have a bulk upload or excel import/upload options in the Projects/Tasks/Issues pages for saving time when the user enter multiple items at a time.Everytime its not easy and time taking to reach the admins to upload via Kickstarts as it would take more time to prepare the import excel and getting the object IDs in the acceptable format and so on.
Must have - import projects and templates from EXCEL files, not only MS project. why can we export as excel but not import??? it will save hours hours of unecessary work for templates adjustments.
DescriptionCurrently in Workfront, logging hours on a task requires Contribute permission, which also grants the ability to edit certain task details (such as the task name). This creates a governance challenge for organizations that need accurate time tracking but also want to maintain strict control over task data.Why is this feature important to youAccurate time tracking is essential for reporting, resource planning, and performance analysis. However, allowing users to edit task details just to log hours introduces risks of unintentional or unauthorized changes. For organizations with strict process compliance, separating time entry from task editing is crucial to maintain data integrity and governance.How would you like the feature to workIntroduce a standalone “Log Hours” permission that can be assigned independently of Contribute access. This permission should allow users with View rights on a task to enter time without being able to modify any other task attributes. It should be configurable both in access levels and in sharing settings to provide flexibility across different teams and roles.Current BehaviourCurrently, users have Contribute access to log hours on a task. This access also allows them to edit key task details, which creates a risk of accidental or unauthorized changes. There is no way to enable time entry without also granting broader editing capabilities.
Description - It would be great if we had the ability to to pin views, filters, and groupings in individual projects. Why is this feature important to you - It would allow us to already have the preferred view, filter, and grouping set when navigating to a project. This is especially helpful when navigating between normal projects (where assets are created) and request queues (where we typically have unique views, filters, and groupings set). How would you like the feature to work - Similar to how you can pins items to the top of your screen, we could have a way to pin (or remove pin) for the view, filter, or grouping within a project (where the information is selected from). Current Behaviour - Inability to keep preferred view, filter, and grouping within a specific project. It must be manually changed each time you navigate between them.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.