5.3.2 Functions used during debug operations

Interruption settings for debug operations

There are two ways to execute a debug task:

• Do not break after each step

  Like execution of a normal task, processing of the debug task proceeds without pausing between steps. You can check the execution results of the debug task and identify steps where issues occur.

• Break after each step

  Execution of the debug task pauses between each step. This allows you to check the values of plug-in properties and return values step by step.

5.3.4 Procedure for starting the debug process, 5.3.7 Flow of debug process without pausing between steps, 5.3.8 Flow of debug process when pausing between steps

Displaying flow information

There are two ways to display the flow of a debug task:

• Flow view

  In the service template debugging view and Tasks window, you can view the status of steps and the flow transitions at each hierarchical level.

• Flow Tree view

  In the service template debugging view, you can view flow hierarchies in tree format. You can also identify paused steps in each flow hierarchy.

  You can also view flow hierarchies in tree format from the Tasks window.

5.3.24 Displaying the flow of a debug task, 5.3.25 Displaying the flow tree of a debug task, 5.4 Managing debug tasks

Displaying task logs

The contents of the task log appear in the Task Log tab of the service template debugging view. You can configure JP1/AO to automatically refresh the contents of the task log.

5.4.4 Procedure for checking task log entries for debug tasks

Checking property mapping

You can display the values of plug-in properties and the property mapping settings in the Debug view. By viewing this information together with the service property values displayed in the Properties tab of the service template debugging view, you can check whether property mapping is set up correctly.

5.3.16 Procedure for checking property mapping settings during debugging

Changing information in a step^#

You can change a property value or return value of a plug-in to any value.

• You can pause a step before its plug-in processing is executed and change the value of input properties.

• You can pause a step after its plug-in processing is executed and change the value of output properties or the return value of the plug-in.

5.3.17 Procedure for changing the value of a plug-in input property during debugging, 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

Skipping plug-in processing^#

You can skip plug-in processing and continue processing as if execution of the step had completed.

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

Retrying tasks

There are two approaches to retrying a failed debug task:

• Retry the task from the failed step

  You can resume task execution from the failed step.

• Retry the task from the step after the failed step

  You can resume task execution from the next step, as if the failed step had finished normally.

5.3.13 Procedure for retrying a task from a failed step during debugging, 5.3.14 Procedure for retrying a task from the step after the failed step during debugging

Managing debug tasks

You can perform the following operations in relation to debug tasks:

• Display a list of all debug tasks

• Stop execution of a debug task

• Forcibly stop a debug task

• Delete a debug task

5.4 Managing debug tasks