5.3.12 Procedure for skipping plug-in processing during the debug process

If there are plug-ins whose processing you do not want to execute during the debug process, you can skip the processing of those plug-ins. You can specify the values of output properties and the return value of these plug-ins so that it appears to the next step as if the plug-in has executed. This allows you to assess the effect the subsequent-step execution conditions have on the status transitions of steps and tasks, flow transitions, and the processing of subsequent steps.

For details on plug-ins whose processing cannot be skipped, see 5.3.10 Plug-ins that cannot be paused during debugging.

Note that you can only skip plug-in processing when Interrupt After Each Step is selected as the break setting for the debug process.

To skip plug-in processing:

1. With the step whose plug-in you do not want to execute paused, select Do not execute the plug-in processing from the Execution Settings list box in the Debug view.

2. In the Return Value text box, specify the value you want to use as the return value of the plug-in.

   The return value you specify determines the status transitions of steps and tasks and the flow transitions, subject to the subsequent-step execution conditions.

3. Specify values for output properties as needed.

   Tip

   If you have configured output property mapping, the value you specify for an output property is passed to the service property (output property or variable) to which it is mapped. If you do not specify a value, the service property (output property or variable) to which the output property is mapped will have a null value.

4. Click Rerun.

Related topics

• 5.3.4 Procedure for starting the debug process

• 5.3.9 Processing of debug process when pausing between steps

• 5.3.18 Procedure for changing the value of a plug-in output property during debugging

• 5.3.19 Procedure for changing plug-in return values during debugging

• 3.2.4 Overview of subsequent step conditions

To Page Top