Last updated
Was this helpful?
Testing a workflow is the recommended way to verify its functionality, appearance, process flow, and the actions it triggers in Command Centre. Every workflow should be tested before publishing. Once published, a workflow cannot be set to testing again.
The testing function is also useful when changes to a published workflow are required. By using the Testing status on a new workflow version, you're able to test changes without interrupting the active and published workflow instance.
Only one workflow version can be tested at a time.
To set a workflow version for testing, use one of the methods below.
You can edit the workflow in testing mode. Remember to save any changes you apply.
In the sidebar, in the Actions column, click the three-dot menu and select Test. This changes the status of the selected workflow version to Testing and makes it available for testing in the Workflow Management module.

You can also set the workflow to testing directly from the workflow editing screen in the workflow builder.
The module displays a list of workflows. In Workflow Builder, either open an existing workflow for editing or create a new one.
Open the workflow for editing and click Test in the top bar. This changes the status of the selected workflow version to Testing and makes it available for testing in the Workflow Management module.

After clicking Test, confirm that you want to set the workflow to testing mode. The workflow version is now available for testing in the Workflow Management module.
Click on the workflow to access options for managing visibility post-publication and executing test versions.
Click the Run Test Version button to view the workflow execution. After testing, you are returned to the Make a Request dashboard. Repeat the testing as needed by revisiting the Workflow Management module.
All actions executed by the workflow in the Command Centre during testing will affect the Command Centre environment integrated with AccessNow.

To test the parts of the workflow that are not visible to the requester, such as approval, you must use an approver account or ask a privileged approver for help. Then check that the approver part of the workflow is also working correctly.
This task separation is due to the fact that no user can approve their own requests, even if they are just test requests.
After finalizing your workflow, you can move forward with publishing.
Last updated
Was this helpful?
Was this helpful?

