Test Mode lets workflow Editors or Creators run workflows before publishing or after changes. Use Review & Test, resolve errors, select a school and tester email, complete the trigger form, and perform tasks through My Tasks. Monitor progress and automated actions in Workflow Run. Completed tests are labeled “Test”; changes must be republished to affect the live workflow. Testing a workflow will also test Arbor Data Steps which will require manual removal from the MIS.
Whether you're building from scratch, or building from a Template, testing your workflow is always recommended before launching it. It is a great way to run a workflow from start to finish and check what all the steps do and how it runs. It means you can check that the workflow does what you expect, and that the wording and layout is all correct before deploying it. If you make changes to a workflow after it has first been published, those changes will remain in 'Test' (and not the 'Live' version of the workflow) until you republish it. This means you can run a workflow in Test mode to check those changes before you Publish them.
What is Test Mode?
Before publishing a new workflow, making changes to a Template or amending a current workflow, it's a great idea to run a test of that workflow. The 'Test Workflow' function allows you to run your workflow as if it was live → the only difference being that any communication or action is directed to the tester’s email address, rather than to the Roles who would receive emails or tasks if the workflow was running in Live.
To be able to run Test Mode - you must be an Editor or Creator of the workflow.
How do I start a test workflow?
When viewing a workflow in the editor, the ‘Review & Test’ button will be visible in the top right-hand corner.
You must ensure the workflow is free of errors before testing. If you select Review & Test while they are present, you will be prompted to fix them, as below.
Once you have fixed any issues or, if there were none and you select Review & Test, you will be taken to the Review area.
You can use this area to configure your workflow, this information will be available for your 'test' workflow as well.
Once you are happy with this area, or want to review it later you can select 'Test workflow' towards the top of the screen.
Running the test
Selecting ‘Test Workflow’ will open a pop up.
From here, you will be able to select which school you would like to test the workflow for, using the drop down menu. This is important, as it will control which information Arbor Workflows will pull from i.e. for Assets.
Select the relevant school, ensuring that the test email address appears in the address bar in the top right-hand corner. If you are the one running the test, make sure your email is populated in the address bar.
The email provided here will drive the test workflow, with all emails, approvals, checklists, forms and update actions being sent here.
Once you have checked the test email and selected a school, you can select Start test.
This will open a new tab for you to populate your trigger form with information to start the test workflow.
Once you have completed the trigger form and pressed submit, the form will trigger the next step in your workflow. You can carry out the steps in that test by navigating to the 'My Tasks' area of Arbor Workflows. Here you will be able to see any tasks which are waiting for you, to see the context and complete the task.
Once you have completed any task that needs your attention, you can refresh 'My Tasks' to see the next Task for you to do. At each stage, you’ll complete the forms and tasks as if you are the recipient, entering test data. These actions will also be sent to the tester's email which lets you see how the 'real' recipient will receive the notification.
It is also a great idea to track the progress of your Test workflow by viewing each step in your 'Workflow Run' area. Again, you can refresh the page to make sure it is showing things move from step to step. From here you can also see what has happened in 'automated' steps e.g. emails and check the contents:
You can also select the down arrow next to each step to expand the information about each step.
Completing your test
When you have finished testing each of the steps in your workflow, the workflow run page will be marked as complete and it will have a 'Test' label.
From here, you can also access any PDFs you have set up to be available on the workflow run information by selecting the paperclip icon. This will open a drop down of any available PDFs for this workflow run should you see to view or take them outside of workflows.
If you need to make any changes you can navigate back to the workflow editor to make these as a result of the test. Any changes will need to be published again to reach the live version.
If your workflow includes any Arbor Data steps, which will have been actioned as part of the test and will require manual deletion, if needed, your for MIS.
Comments
Article is closed for comments.