Running a Process in Test Mode

Running a process test allows you to evaluate all steps and forms within a process in a streamlined and time efficient manner by utilizing process test rules and by marking process iterations as test runs. This document provides an overview of how the test process works.

A test process replaces production destination information with designer specified details based on process test rules. In addition, test instances will be marked in the Monitor page for easy recognition, and test tasks will be marked in the Inbox of the user assigned to each task.

Free Training: New Streamlined Testing and Troubleshooting in Forms 12 eLearning course in Aspire.

Testing Forms Processes

About Process Test Rules

The use of process test rules eliminates the need to manually reconfigure user tasks and service tasks for testing purposes, reducing the time spent on testing and speeding up overall process deployment time. It allows organizations to safely test internal or public-facing forms without disrupting the live environment or cluttering up production data.

Process test rules simplify process testing in the following ways:

  • Prevents confusion and churn from test emails for users.
  • Ensures emails and tasks are correctly sent and assigned without manual follow-up.
  • Eliminates the need to delete test folders and documents after test completion.

For any process open in the process designer, in the left pane select Process Test Rules to display, create, and configure the test rules.

Test rules have three primary configurable options: Replace, With, and For. For example, using a test rule you can Replace the User task assignment With the user that initiated the process (using the variable /_initiator) For All user tasks.

New processes include two default rules:

  • Replace: User task assignment
    With: Initiator (/_initiator)
    For: All user tasks
  • Replace: All email addresses
    With: Initiator (/_initiator)
    For: All emails

Configuring process test rules

  1. To add a new rule, click the + Add Rule link.
  2. The Replace field allows selection of what type of data to replace, All email addresses, Save to repository path settings, or User task assignments.
  3. Specify what value to use for the test. Process variables can be used in this field.
  4. The For field will have different options available dependent on the selected data type under Replace.
    • When All email addresses is selected, the options are All emails, These types, or These individual steps. This allows for greater control for testing. All emails will replace the addresses in all steps including process notifications. These types allows for the selection of All service tasks, All user tasks, or Process Notifications. These individual steps allows for the selection of one or more steps in the process.
    • When Save to repository path settings is selected, the options are All save to repository service tasks or These individual steps.
    • When User task assignments is selected the options are All user tasks or These individual steps.
  5. Use the Enable test rule toggle to turn on or off a specific rule.
  6. When there are multiple rules, the order in which they are applied can be set so that a complicated set of rules may be created to suite the needs of the team. Use the arrows to move a rule up or down in the order.

Starting a process test

To start a process, from the Process Diagram click the Test process button (Icon: bubbling Erlenmeyer flask). A confirmation dialog will show the active test rules that will be applied. If there are no active test rules, a link to the Process Test Rules page will be provided. Click either Start to begin the test, or Cancel to cancel the test.