Skip to main content

Ideas

Filter by idea status

10000+ Ideas

AlexCa20Adobe Employee

Increase Calculated Field Limits in PlanningNew

ContextAn enterprise customer implementing Adobe Workfront Planning encountered a platform‑imposed limit of 20 calculated fields per record type while trying to add a few additional calculated fields to support new teams. They asked whether this restriction could be overridden.Steps takenSupport investigated and confirmed that Workfront Planning currently enforces a hard limit of 20 calculated fields per record type. This limit is part of the product’s performance guardrails and cannot be changed or increased within an individual customer environment.Business impactThe customer is using a single, centrally governed workspace to maintain consistent intake, taxonomy, and reporting across multiple lines of business. Calculated fields are a core component of their sizing, normalization, and reporting logic. The 20‑field cap forces them to:Remove or consolidate existing calculations Introduce manual workarounds Fragment their data model across multiple record types or workspacesThis undermines their goal of using Planning as a centralized, enterprise‑grade planning system, slows down their rollout, and risks reduced data quality, higher operational overhead, and limited scalability as more teams onboard.The askWhy does the 20‑field limit on calculated fields exist in Workfront Planning? Is there any plan or timeline to increase or remove this cap? Given that this limitation has surfaced for multiple organizations, what is the recommended enterprise design pattern or workaround when the need clearly exceeds 20 calculated fields per record type?

Workfront Fusion Enhancements for Message Context, Execution Visibility and Notification/Error LogsNew

SUMMARY FOR WORKFRONT FUSION detailed Observability requirements.We are working on offloading the Workfront Fusion logs to Splunk and have explored the recently shared Workfront fusion activity log api . Below are the enhancements we are looking to get from Workfront Fusion platform._______________________________________________________________________1.Fetching Notification Logs (Execution State/Errors/history)•    Currently Fusion maintains execution logs for each scenario, and you can view these logs in the Fusion UI under the scenario’s execution history.•    Enhancement: Is there a way to fetch notification logs or see where they are stored (e.g., scenario stopped, execution errors)?________________________________________2. Enhanced Message Field for Module Actions (Create/Delete/Modify/etc.)•    Currently, Fusion logs actions such as module creation, deletion, and modification, but the log messages are not highly descriptive about the specific changes made.•    Enhancement: Is it possible to enhance the message field for all actions on scenario modules? More detailed logging (e.g., which field or configuration was changed) for audit and troubleshooting purposes.________________________________________3.Enhanced Message Field for Scenario Scheduling ChangesCurrent Behavior:When you activate, deactivate, or update a scenario schedule (such as changing the frequency), the audit log or message field records a generic message like <user> updated <scenario>.•    Currently, the message field does not provide granular details about what specific attribute (like frequency) was changed.•    Enhancement: Can the message field capture more details (e.g., “changed the frequency to 30 mins”)?________________________________________4.Retrieving “Folder” Details Alongside Other Properties•    Currently, Fusion scenarios and modules do not natively expose a “folder” property in the API responses.•    Enhancement: Is there a way to get “folder” details with properties like teamId, entity, etc.? 

DavidGu14Level 2

Workload Balancer UpdatesNew

The Workload Balancer is one of the most useful tools within Workfront but could be made even better with some quality of life updates.Ability to extend the length of time you’re viewing.  Right now there are limitations on the number of weeks or months you’re allowed to view (only up to 12 weeks/3 months).  Extending the ability to view as long as 6months to even a full year would be helpful. We see a variety of use with entering and managing allocations. Some teams enter allocations for the year on a handful of tasks and redistribute allocations as needed on a monthly basis when changes occur. Others focus on the more granular allocation to short-duration tasks that they need to see totals by day but over a period of several months. Clear allocation to capacity comparison on the screen. A toggle to turn this on/off and display on screen rather than only having the pop up that shows you this information.  Correcting the Workload Balancer so that when hours get contoured in the WLB and then dates later change the updates respect the project schedule and do no put planned hours on weekends.  This is a known and ongoing issue that needs to be corrected. If durations change and you don’t have the same number of days to put hours on, just revert to spreadhing the hours evenly with a warning message to the user they have to accept. Ability to show/hide weekends for companies that do not schedule work on weekends. (Obviously need to fix the issue with Contouring before this can be an option.)  This would be another setting that can be toggled on/off.