8.3.11 Procedure for skipping plug-in processing during debugging
You can skip processing of plug-ins that you do not want to execute during debugging. To skip plug-in processing, specify the output property values and return value of the step on the assumption that the plug-in processing is performed. 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.
To skip plug-in processing:
Interrupt the step that contains the plug-in you want to skip before processing of that plug-in is performed.
In the Debug area, from the Debug Modes pull-down menu, select Run plugin in dry-run mode.
Execute the step until plug-in processing is performed, and then interrupt execution. If breakpoints are set for the step containing the plug-in you want to skip, click the Resume button (
). If no breakpoints are set, click the Step Into button (
).
In the Step Properties area, click
for the return value, and then specify the desired value.
The return value you specify determines the status transitions and the flow transitions of steps and tasks, subject to the subsequent-step execution conditions.
If necessary click
for an output property, and then specify the desired value.
- Tip
If you have configured output property mapping, the output property value you specify for the step is applied to the service property (output property or variable) to which the output property 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.
Operation results
If you perform an operation that executes a process, debug task processing goes on according to the specified return value and output property.