Disabling Workflow for Applications

You can disable workflow at the application level so that requests made in that application will bypass all active policies when the request is submitted.

This can be helpful, for example, when you want to change data in your test environment without having to go through the workflow process.

Considerations

• Disabling workflow for an application does not disable the individual policies for that application. When you resume workflow, all enabled policies go back into effect. To disable an individual policy, see Modifying Policies.
• The Disable Workflow setting does not affect existing requests which have already been submitted. Only newly submitted requests will bypass active policies.
• This setting does not get transferred when you transfer an application using a template. That is, if you disable workflow for an application in one environment and then transfer that application to another environment, workflow is not disabled for that application in the second environment.

To disable workflow for an application:

1. Inspect the application. See Inspecting Applications.
2. On the General tab, select Disable Workflow to have requests made in the application bypass all active workflow policies.
3. Optionally, use the Submitted By parameter to limit the bypassed workflow to requests submitted by the selected users only.