...
| Column | ||||
|---|---|---|---|---|
There are two ways you can test your workflows. Method 1: Click the Method 2: Click the Both methods display the test mode popup which includes the Test Mode Views discussed below. It is important to note that both Test methods allow the designer to test the steps of a workflow until the workflow is routed to a different user. Once a step is routed to a different user, testing must continue by Using the Task List. For example,
|
...
When the 
save and test is clicked, the workflows is saved in the background, and the Test frevvo Test popup window displays reflecting the newly saved version of your workflows. The workflows will behave exactly as it will when users access it. To test the workflows, just complete it as your users would and click Submit. When you close the Test popup, you will be on whatever designer page you were on when the save and test icon was clicked. This allows the designer to go right back to making changes after closing the Test popup.
...
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Step Assignments for Testing
Usually as the designer you want to test the workflow's behavior, including Task Notification emails and business rules that execute on each step. However, you may be hesitant to test your workflow with real User and Role assignments, which will notify these users with each test. One idea is to set up dynamic user and role assignments that will assign each step to test user(s)/role(s) when the workflow is started under a testing condition, such as initiated by the designer user, and otherwise will use the as-designed step assignments. This pattern will allow you test workflows fully in development or production without notifying and cluttering the task list of real users.
First, add a test role and one or more test users, whose emails are are set to your own email(s) so you will be able to view Task Notification and Doc Action emails.
Let's say you have a workflow with three steps. Step 1 is performed by any user, Step 2 is assigned to the user's manager, and Step 3 is assigned to the role "HR". Instead of hard coding these assignments, use controls in your form to set the Manager user and HR role values. Set the step assignments to the template for those controls, i.e. Step 2: {Manager} and Step 3: {Role}
Then add a business rule that checks the initial user's id - if it happens to be "designer", then set the control Manager to your test manager user (mgrTest) and set the control Role to your test role (HRtest). The else action sets these controls to the initial user's manager and the real role "HR".
Test the workflow from your designer user account. You will receive the Task Notifications via your test user's email, and you can log in as the test user(s) to perform the tasks.
When you're ready, start the workflow from some real account. Now it should route through the real-world assignments as expected.
