cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Workflow-driven Section Visibility in Autodesk Fusion Manage (beyond Permissions)

Workflow-driven Section Visibility in Autodesk Fusion Manage (beyond Permissions)

Background
In Autodesk Fusion Manage, sections within a workspace can currently only be shown or hidden based on permissions (roles/ACLs). This approach is limited when processes are strongly workflow-driven.

This limitation is especially visible in the Change Requests workspace. When creating a new change request, it would be beneficial to initially display only a minimal set of fields (e.g. “Initial Request”). Additional sections—such as analysis, impact, decision, or implementation—should become visible progressively as the workflow advances.

Problem Statement
Currently, this type of control is not possible because:

  • Section visibility cannot be controlled based on workflow states or transitions
  • Only static visibility via permissions is supported
  • Workarounds (e.g. separate workspaces, validation scripts, UI extensions) add unnecessary complexity

This results in:

  • Overloaded forms during data entry
  • Increased risk of user errors (fields visible too early)
  • Higher training effort
  • Reduced process guidance within the system (users must know what to do instead of being guided)

Proposed Enhancement
Introduce workflow-driven section visibility, allowing configuration such as:

  • Section visibility based on:
    • current workflow state
    • optionally: workflow transition (event-based)
  • Configuration similar to permissions, but extended with workflow logic

Example configuration:

  • State “Draft” → only section “Initial Request” visible
  • State “In Review” → additional section “Review / Impact” becomes visible
  • State “Approval” → further sections for decision and approval become visible

Optional extension:

  • Differentiate between:
    • visible / hidden
    • read-only / editable

Benefits

  • Clear process guidance directly in the UI
  • Reduced need for scripting or structural workarounds
  • Improved data quality (information captured at the right stage)
  • Better scalability for complex workflows

Use Cases

This feature is not limited to Change Requests but would also be valuable across other areas in Autodesk Fusion Manage, including:

  • Requirements Management (e.g. staged requirement definition)
  • Change Orders / Problem Reports
  • Quality processes (CAPA, audits)
  • Any multi-stage review or approval workflows
2 Comments
Jack_DuttonTM2JK
Enthusiast

This would give a bunch of need flexibility!! Love the idea! +1

torben.westhoefer
Contributor

This would be great!

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea