This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Specifying human task emulation values in the integration test client

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
If a human task emulator is encountered during a test, the test pauses at a Claim event and you need to either specify some output parameter values or select an exception to throw. Specifying output parameter values for a human task emulation is accomplished in exactly the same way as specifying initial request parameter values for an operation, as described in the topic "Specifying operation values".

Before you begin

Before you can specify human task emulation values in the integration test client, you need to create a human task emulator and configure it as described in the following topics:
  • "Adding human task emulators"
  • "Specifying a wait time for human task claims"
  • "Specifying a potential owner for a human task"

About this task

To specify human task emulation values:

Procedure

  1. Launch the integration test client from the business process that contains your human task.
  2. In the Component field of the Events page, select the name of your component that runs the human task.
  3. In the value editor, specify an initial request parameter value in the Value column.
  4. Click the Continue icon Picture of the Continue icon. A Claim event is generated into the Events area when the human task is run.
  5. In the Events area, ensure that the Claim event is selected.
  6. In the value editor, specify output parameter values for your human task emulator.
  7. Click the Continue icon Picture of the Continue icon. A Return event is generated into the Events area and the return parameter values are displayed in the value editor.

What to do next

When you have finished specifying human task emulation values, you may want to reinvoke the operation or generate an Invoke event to invoke and test a different operation. These tasks are described in the topics "Reinvoking operations" and "Generating Invoke events." Or you may want to save the test trace, as described in the topic "Saving test traces."