Skip to main content

Ideas

Filter by idea status

10000+ Ideas

Raymundo2New Member

Enable CA Certificate Auth Support in Anaplan Standard Modules within FusionNew

Description -The current Workfront Fusion Anaplan connector only supports CA certificate-based authentication for custom API calls via the HTTP module. The standard Anaplan modules (e.g., Run Export, Get File, Run Process) do not support CA certificate-based connections, limiting their usability for customers who have adopted certificate authentication for security and compliance.Why is this feature important to you -Our clients organization and many large enterprises enforce CA certificate-based authentication for Anaplan as part of IT security policies. Without native support for this connection type in the standard Fusion Anaplan modules, we are forced to reimplement core Anaplan actions using low-level custom API calls, increasing development time, reducing maintainability, and exposing us to higher error rates.Full support for CA certificate authentication would allow us to take advantage of Fusion's no-code modules for Anaplan without compromising compliance or system integrity. How would you like the feature to work - We would like the standard Fusion Anaplan modules (such as Run Export, Run Process, Get File, and Upload File) to support selecting an Anaplan connection that uses CA certificate-based authentication, in the same way these modules currently support Basic Auth or OAuth connections.Ideally, this would simply involve enabling CA-cert-based connections in the existing “Connection” selector dropdown used across Anaplan modules. Current Behaviour - The standard Anaplan modules in Workfront Fusion only accept connections using Basic Auth or OAuth. If you configure an Anaplan connection with a CA certificate, it is only usable inside custom HTTP requests via Fusion’s HTTP module, and not within any of the built-in Anaplan modules. This restricts functionality for organizations that enforce CA-cert-only authentication.

Farzaneh
FarzanehLevel 4

Adobe Workfront Mobile AppNew

Description:We would like Adobe Workfront to expand mobile app capabilities beyond basic task management. A key missing feature is the ability to access reports and dashboards through the mobile app, particularly when those links are included in Workfront system notifications. Why is this feature important to you:We use dashboards that consolidate custom form data into reports, which are embedded within each project and shared via system generated email notifications. These reports provide critical project updates to our users. Currently, when users receive these links on mobile, they cannot open them within the Workfront app. Instead, the links open in a web browser, where formatting issues make the content nearly unreadable. This limits usability and makes it difficult for stakeholders to stay informed on the go. How would you like the feature to work:When a Workfront-generated notification includes a report or dashboard link, tapping the link on a mobile device should open the relevant report directly within the Workfront mobile app or mobile browser, preserving proper formatting, readability, and alignment. Ideally, the mobile app would support viewing and interacting with standard reports and dashboards, including filters, drill-downs, and custom form data visualization. Current Behaviour:Currently, links to reports and dashboards are rendered as plain text in the project updates within the app, and when tapped, they open in the mobile browser. In the browser, the layout is distorted and difficult to read, with alignment and formatting issues that degrade the user experience. There is no current support in the Workfront mobile app for accessing reports directly.

Overriding User Job Role in Assignments to calculate accurate planned/actual revenue figures for TasksNew

Description / Current behaviour:If a Task has Revenue Type = Role Hourly [With Cap / Plus Fixed] setting, the Planned & Actual Task revenue is calculated with the Billing Rate associated with the Assignment Role(s) of the Task.The Billing Rate applied may be the default one set on the Job Role, or one that is set on the Company / Project for that particular Job Role.If a Task has multiple Assignments, revenue is calculated for each of them separately (using Assignment Role) and then summed.For User Assignments (as opposed to Role Assignments), the Assignment Role (labelled as "Assignee's Role" on the UI) can be (only) one of the Job Roles associated with the assigned user.The following business problem exists with this scenario:A task is planned with Job Role X and sold to a client at a price calculated with Job Role X.Given task is assigned to a user with Job Role Y (since a user with Job Role X is not available)The Assignment Role will be Job Role Y, i.e. the Job Role of the User.Workfront calculates the planned / actual revenue of the Assignment using the Job Role of the user (Job Role Y).Consequently, the planned/actual revenue of the assignment (and of the Task and Project) is incorrect, since the correct figure would be calculated using Job Role X.How would you like the feature to work?When editing Assignments of a Task, any active Job Role can be specified as "Assignee's Role" not only the Job Roles associated with the assigned user.The planned / actual revenue for the assignment is calculated with the Assignment Role (as it is now).Role Hourly revenue can be calculated with any role, not only with one of the assigned user's own roles.For convenience, project level default assignment roles can be defined for each project team member.If a project level default assignment role has been defined for a user, when that particular user is assigned to any task on that particular Job , the "Assignee's Role" (Assignment Role) on the new Assignment will automatically be set to the user's project level assignment role.It should be possible to manually change the Assignment Role to any Job Role.When setting a project level assignment role for a user, the Assignment Role of this user on this project on existing Assignments is not changed.Configuring project level default assignment roles can commence either on the "People" tab of the project or in a new Column labelled as "Default Job Roles".Project level default assignment roles can't be date effective. They apply to the project regardless of the date.The proposed way of working will be really critical to our new core design!

CoriZufelt
CoriZufeltLevel 2

Bring back Search window close button and persistent filtersNew

Description: The Search UI has recently changed in Workfront removing both the ability to simply close window when finished searching to return to the page you were on and the ability to have your search filters per object type persist.This change impacts our user base negatively enough that we assumed it was a bug and I put in a support ticket. I've received the following response: What Changed in the Workfront Search UI?Full-Screen Search: The Advanced Search is now a full-screen experience. When you open the search, it overlays the entire page.No Close Button: The new design does not include a close (X) button to exit search and return to your previous page. Instead, you must use the browser’s back button.Navigation Impact: If you perform multiple searches or add filters, each action adds to your browser history. Returning to your starting page (e.g., a project) requires multiple clicks on the back button, which can be cumbersome.Consistency: This behavior is the same across Chrome and Firefox, on both Windows and Mac. Why Was This Changed? According to Adobe Workfront’s official documentation: The Advanced Search is now full screen. You must navigate away from the page rather than closing the dialog.This update is part of a broader interface modernization effort to make Workfront more consistent with other Adobe applications. However, it has unintentionally reduced usability in this area. Known Limitations and User ImpactThere is no way to simply “close” the search and return to your previous context. The filter is not prepopulated and does not persist after a refresh. The only way to return to your previous page is to use the browser’s back button, which can be tedious after multiple searches or filter changes. This affects all users and is not browser- or OS-specific. Workarounds & RecommendationsUse the Back Button: For now, using the browser’s back button is the only way to return to your previous context. Open Search in a New Tab: As a workaround, right-click the search menu and choose “Open link in new tab” (if available), so your original page remains open.  Why is this feature important to you: Being able to simply close the search window when done searching is the simplest most efficient user journey especially if you are trying to eliminate user clicks as much as possible. Right now, with the update in place, if you perform a search and then add multiple filters in order to narrow down your search you will have to have either remembered to open a new window/tab for searching alone or will be forced to click the back button in your browser multiple times to return to your original page. Filters you set no longer persist to the next search which necessitates this multiple iterations in the search window every time you use it unless you want to use a simple, very generic search and not drill down past the first page of results If this is aligned to how search works in other adobe products, search should be updated across their whole product offering because this experience is terrible.How would you like the feature to work:1) Primary concern: Bring back the close button so you can simply close the search window at any time to return to the page from which the search window was opened2) Secondary concern: Allow filters to persist in the search window