Complete Guide to Testing Workflow

This article highlights how to test Workflow yourself, as a single person, reviewing the experience of all roles in your given process. Of course you can build on this approach to involve others in your test, if needed.

Beta

Please test all your Workflow processes in the Beta environment! It will give you full control over who is affected by the test and it will allow you to test immediately because Schedules are configured to auto-launch in Beta. Testing in Beta also helps keep Production clear for your real content.  

Prepare the User Accounts for Your Test

We recommend testing Workflow with test accounts, especially if you’re an administrator and need to experience Workflow from the perspective of each role that will be involved in your process.

Once you’ve created the process template, take a spin through the steps in that template to see how many different types of users are involved. For example, if your steps are Faculty Member Department Committee Department Chair Dean you’ll need to create accounts for each of the process participant types:

  • Faculty member who is the subject of the pilot process
  • Department Committee member
  • Department Committee Chair
  • Department Chair
  • Dean

Now that you know how many test accounts you need, create your test accounts. We recommend using a model like this for each one so you can easily set and recall the login information:

Users and Security field Faculty member Department committee member
First Name Test Test
Last Name Faculty Committee Member
Email [your personal email address] [your personal email address]
Username testuserf testusercm
Authentication Local Local
Do we need to keep track of this user's teaching, research and service activities? Yes No
User attributes Chosen Department, College, etc. N/A
Security Role Faculty Faculty

Because the user accounts in the Beta environment refresh every Saturday, we recommend either a) configuring the accounts early in the week so you have the rest of the week to test or b) configuring the test accounts in Production on a Friday so that the following week they’re ready for you to use to test in Beta.


After you create your accounts, reset the password for each one:

  1. Click the pencil next to the username to edit the test account
  2. Click “Reset Password” at the top of the page
  3. Check your email for a password reset link and follow the subsequent instructions
  4. Once you’ve reset the password, log out of that test account.

Repeat this sequence until you’ve established the passwords for each test account.

Add Data to Your Test Faculty Account

You’ll also likely want to test generating a custom report as part of the faculty step. To do that, you’ll need to give your Test Faculty Member account some data. Just log into that account, go to Manage Activities, and add a few records like publications, courses, and service records within the report date range.

Set Up the Role Groups to Support Your Test

Once you have your accounts in hand in the Beta environment you can configure Role Groups in Workflow to support your pilot test. Go back to that list of steps in your process Template and create a Role Group for each one. In each role group, be sure to assign the test accounts you created to the Role Group for the right step. For example, if you’ve chosen to run this test for Department A, you’ll need to assign your test committee member and test committee chair to the Review Committee Role Group for Department A.

See the MANAGING ROLE GROUPS Resource Center section for details on how to create role groups.

Set Up the Test Schedule

Now that you have your Role Groups ready for your test, create your test Schedule.

  1. Choose a launch date of tomorrow.
  2. Choose any step due dates you’d like.
  3. If you included one or more custom reports in your faculty step, set a report date range that you know will pull in the sample records you entered for your Test Faculty Member.
  4. When selecting subjects, choose the department to which your Test Faculty Member is assigned.
  5. For each reviewer step, select the Role Group that houses your test account(s) for that type of participant.
  6. Select “Confirm”.

Give the process a minute or so to launch.

Note: reminder emails are suppressed in the Beta environment. If you want to see them, let your Success Consultant know and they can forward them to you.

Test the Process as Each Participant

Now that you’ve launched your process, you can start working your way through the process as your participants will. To experience what participant will see:

  1. Log in through the test account earmarked for that step
  2. Fill in that test account’s form in their Workflow task
  3. Submit the test account’s Workflow task
  4. Log out of that test account and into the next in the sequence
Note: One small oddity in testing this way is that the ability to monitor the status of submissions only opens on the specified launch date. So even though your Schedule auto-launches in Beta, you won’t have access to monitor the status of submissions for your pilot Schedule until the launch date you specified when configuring the Schedule. Once that day arrives, though, navigate to your test Schedule and click the action arrow and then “Submissions” to view the status. If you completed all of the steps in the submission for your Test Faculty Member, the submission for Test Faculty Member should no longer appear in this list, indicating that it is complete.
Was this article helpful?
0 out of 0 found this helpful

Articles in this section

How to Contact Support
Click the "Submit A Request" button at the top right or bottom of the screen to create a case.
Watermark Academy
Click to access the Watermark Academy for free webinars, workshops, certifications, and free on-demand training