Workflows in classic and next-gen projects

In classic projects, workflows are independent of request types. This means multiple request types can share the same workflow. Changing a workflow will impact every request type associated with it. Workflows have their own place in your project settings.

In next-gen projects, each request type has its own workflow. Changing a workflow only impacts that specific request type associated with it. Since workflows are attached to a request type, you edit a workflow by going to its associated request type. You can copy workflows across request types, but they become independent after copying. Copied workflows aren’t updated simultaneously when a change is made to one of the request types.

 

Diagram to show classic workflows can be shared across request types, and next gen workflows are request type independent

Additional Help

Ask the Community