Test Workflows & Tasks

Before rolling out your new Workflow to employees, customers, or partners, you should test it to ensure it’s functioning as expected. As you build out a Workflow, you can even test each individual task.

How to test an entire Workflow

  1. In the Workflow Builder screen, select at the top.
  2. Choose how to run the test:
    • By yourself: Tasks and email actions will be sent to you, instead of the normal assignee’s and recipients. Note that other system actions might affect other people or those systems.
    • With others: Tasks and email actions will be sent to their normal assignee’s and recipients. The name of the instance and tasks will include (TEST) appended at the end.
  3. Select . When you start the test, the test instance page will load.
  4. A test instance is now in progress. Progress through the instance as normal, completing tasks and noting any changes that you would like to make
  5. To end the instance early, Select at the top of the page and then select End Instance

If your Workflow includes a task to automatically start a process for each row, these instances will all be started and marked as (TEST).

How to test an individual task

  1. In the Workflow Builder screen, click an action you would like to test.
  2. At the bottom of the configuration panel, select Open in Previous Editor

    screen readers look here
    Select "Open in Previous Editor". A new browser tab will open. Select "Preview & Test" in the new tab.
  3. Select Preview & Test, then select
  4. The task will process for a moment. When it appears, select the View this test task in a new tab to see the results
  5. If it is an automated action:
    1. If it has not yet completed, wait a moment until it does or refresh the browser
    2. Select the , and select Fields to view the output fields
  6. If it is a task assigned to a person:
    1. Review the instructions
    2. Fill out the fields, testing any field conditions
    3. Select
  7. Note any changes you would like to make, then close the browser tab to return to the Workflow build page

Recommendations when testing a Workflow

If a process does not end, use End this Workflow

If you find a pathway in the Workflow which does not close out the Workflow as desired, add a Workflow: End this Workflow action.

Review the Workflow flowchart to see the structure

You can use the flowchart view to review all task dependencies/conditions and ensure all tasks have been tested. You can access the flowchart from the Workflow build page.

Test a Workflow with delays by temporarily shortening them

If you have multi-day delays in the timing of a Workflow and want to test the Workflow without waiting for the delays, you could temporarily change the multi-day delays to multi-hour delays so that the testing is quicker.

Add stop points while building to prevent runaway processes

Some builders add dedicated “stop” points to their process. This makes it easy to test different sections without the entire process getting kicked off. You could add stopping points with Workflow: End this Workflow.

screen readers look here

Other tips for testing in Catalytic

  • Tested instances are not included in any metrics or Weekly Team Summary emails or reports.

  • Workflow tests are not included in the master data table. However, all data table actions will be performed, so be sure to review and correct any changes which occurred via actions within any imported tables.
  • All task timing will be ignored when testing

  • If there is a deadline configured for a Workflow, ensure the individual task deadlines line up with the overall Workflow deadline. Try working backwards to make sure the dates line up.

  • When testing triggered via email, add Instance Fields which would have come from the email trigger in the Instance Fields to simulate receiving email trigger information during the test.

Experience shows the benefit of extensively testing any Workflow before launching it with other users. Put yourself in the mind of someone who is unfamiliar with this process and ensure your instructions are clear. Try to break the Workflow by not filling out optional fields and inputting unexpected data to see how the automation behaves in a worst case scenario.