Testing Workflows
Use
You can execute workflows and tasks using individual test data. If a start transaction or start form is defined for starting a workflow, this is executed during the test. If the workflow or task is started by a triggering event, you must manually enter values for the import parameters that are normally entered by a binding from the event container.
To start execution, you must be a possible agent for the workflow or task.
Features
In the Workflow field, you can enter the ID of the workflow or the task to be started. This ID consists of two characters for the task type and an eight-digit number. The task type is identified by:
-
TS (for standard tasks) and T (for customer tasks)
-
WS (for workflow templates) and WF (for workflow tasks)
When you enter a customer task, you must enter a blank between the T and the eight-digit number.
On the Input Data tab page, the workflow container or task container is displayed with the current container values. You can enter values required for execution by double-clicking in the relevant container element. You can save a container modified in this way, and re-use it for further tests. Choosing
re-enters the standard values in the container.
On the tab page Deadline Data, you can enter deadlines for the execution of the workflow or task.
On the tab page Outbox, all workflows and tasks previously started by you are displayed. All functions of the workflow outbox are displayed.
On the tab page ad hoc agents, you can determine the recipients of the step for whom ad hoc agent functions are activated. If this is not the case for any steps, this tab page is not displayed.
The selected workflow or task is started using
. After the start, you can go to the Business Workplace, the task definition, or to the graphical or standard workflow log.
Activities
You can access the test environment for starting workflows by choosing or from the Workflow Builder by selecting
.

