FAQ: Moving from Legacy Workflow and Process Tracker
- What happens if I don't enable Configurable Workflows before the retirement date?
- Your tenant continues to use the legacy Workflow and Process Tracker until you enable Configurable Workflows. This legacy functionality is planned for retirement in 2027R1 (targeted for March 2027). Workday recommends that you complete your move to Configurable Workflows well before that date.
- Can I reverse enabling Configurable Workflows after I've enabled the feature?
- You can’t reverse your enablement of the feature through self-service. When you enable Configurable Workflows, Workday deletes legacy processes and resets legacy workflows immediately. You can't clear theEnable Configurable Workflowscheck box fromGeneral Setupafter you enable the feature. If you need to reverse your enablement of Configurable Workflows, your Named Support Contact can log aProduct Supportrequest through the Workday Community.
- Do former legacy process participants automatically get access to the hub?
- No. You must explicitly share the hub with, and assign theAccess Hubspermission to, everyone who needs to view or act on workflow tasks. Workday also doesn't automatically grant theManage Workflowspermission to users who had the legacyManage Processespermission, so you must assign theManage Workflowspermission manually.
- Do I need to recreate my existing level ownership associations for hierarchy submit tasks?
- Not necessarily. If your current level ownership association already reflects the order and participants you want, you can use it as is. If you only need a subset of levels for a given workflow, you can either create a smaller, purpose-built association or clear levels in the enterprise tree when you launch the workflow.
- Is there a limit to how many participating levels a workflow can have?
- There's no hard limit, but Workday recommends that you limit each workflow to 2,000 or fewer participating levels for performance. If your process consistently needs only a subset of a larger association, consider creating a smaller, purpose-built association instead of trimming a large association at launch each time.
- What if a workflow definition shows an error after a system change?
- Errors typically occur when a task destination, hub artifact, or the only assignee tied to a task is deleted after you create the workflow definition. Access the workflow definition to see the specific fields flagged with errors, correct the missing selections, and republish. See Troubleshooting: Configurable Workflows.