How Do I Conduct Operational Tests on a Running Workflow App?

Question.

How do I carry out operational tests when I have modified a running Workflow App?

Answer.

By using the [Debug process execution] feature, it is possible to check the operation without releasing the application.

What's the Debug execution feature?

It is a feature to conduct testing/operational checks on a Workflow App. Using [Debug process execution], you will be able to start a Process for testing (debugging) without [Releasing] the App.

Who will use it? From where will it start?

[Debug process execution] is a feature for Workflow Designers and is available for users who have [App Administrator] authority on the target Workflow App.
You can find it in the properties window of each manual Start Event.

Execution Options

There are some execution options provided in [Debug process execution]. In particular, the option “Allocate all tasks to me” is very useful for the operational check of a Process Model in the developing phase.

The Process will start from the Human Task that immediately follows the Start Event. 

• In [Debug process execution] it is possible to start a Process regardless of the Operator setting of the Swimlane in which the Start Event is located. The User who performs [Debug process execution] will become the [Process Start User].
• [Message Start Event] and [Timer start event] cannot be selected as the starting point. (as of Ver.13.0)

If you wish to start a Process from an automatically triggering Task (such as a [Message Start Event (email)]) you must temporarily place a manual Start Event for the purpose of the test besides it.

Profile

In the cases where [Variables]* are used in the Process Model definition, select a profile for Debug execution. (*This is set in the Edit mode > [Variables Setting])

By using [Variables] you will be able to switch the Email destination or Access URL of the [Throwing Message Intermediate Event] according to the profile. Use this function in cases where you want to send emails to destinations during test runs that are different from the actual operation.

Allocate all tasks to me

Select [Operators] who will handle the Tasks. When this option is checked all the Tasks will be allocated to yourself (the person who operated the Process).

• Checked: All Tasks will be handled by you, not just the first Task.
• Unchecked: The person who starts the process will become the Operator of the first Task. After that, it follows the definition of the App

Management of the Process Started by Debug Execution

The Process started by [Debug Execution] will appear on the [My Tasks] list of the Operator of each Step just like actual Processes. The Issue will proceed according to the Process Model definition and Debug execution options. Also, it will appear in search results if it matches the search conditions.

The differences from normal Processes are as below.

Display Method

The Debug execution Processes are marked with an icon in the Task Operating screen, list of Processes, or Process Details.

Automatically deleted

The Process started by the [Debug Execution] mode will be deleted automatically when the following action occurs.

• [Release] a new version of the App

During Debug execution new numbers will be assigned to the [Process ID], and when the debugging Process is automatically deleted these numbers will appear blank as if skipped.