Process Instance Step Details

Optimize 10.3.0 | webMethods Optimize Documentation | Using webMethods Optimize | Monitoring System Component and Business Process Performance | Viewing Details for a Process Instance | Process Instance Step Details

Process Instance Step Details

About Subprocess Detailed Information

Viewing Steps Within a Subprocess

About Subprocess and Call Activity Duration Time

Viewing a Call Activity Step

To view details for a process instance step

1. In My webMethods: Navigate > Applications > Monitoring > Business > Process Instances.

2. Search for the process you want to work with, and in the search results in the Process Instances window, click the Detail icon (

) for the process instance to open the Process Instance Detail page.

Note:
The

icon is not available for rows representing a subprocess or call activity loop iteration, as there is no additional information available.

3. Click the Step Detail icon (

) to the right of a step in the Step Summary window.

Optimize displays the Process Step Detail page which provides additional information about the step.

The following table describes the information that is displayed in the Step Information panel.

Column	Description
Step Name	Displays the name of the step.
Start Date/Time	Displays the date and time that the step began executing.
Last Updated	Indicates the date and time that Optimize last updated the step.
Instance Iteration	Number of times the process instance executed, including resubmissions. For externally executed processes, this value is always 1.
Step Iteration	Displays the number of times the step executed.
Loop Iteration	Applies only to steps that can be configured for standard looping, such as a subprocess step or a call activity step. A step executes a loop iteration only when a loop condition is configured for the step and that condition has been met. Note: A step can loop two or more times until the loop condition is no longer met. A separate row exists for each loop iteration. Any time the step iteration increments, the loop iteration count is reset and begins again with 1.
Status	Displays the status of the step. Values for this field are the same as the Status values on the Process Instance Detail page described earlier in this section.
Duration	Displays the amount of time that the step took to execute, from the beginning of the step to the end of the step.
Server Type	For webMethods-executed processes, identifies whether the server is an Integration Server or a Task Engine. For externally executed processes, this row reads External.
Server ID	For webMethods-executed processes, identifies the server on which the step executed. This row does not appear for externally executed processes.
Invoked Service	For webMethods-executed processes, identifies the service that the step executed, if the step is a Flow step. This row does not appear for non-service steps or externally executed processes.
Task Detail	For task steps in a webMethods-executed processes, identifies the task that the step executed. This row does not appear for non-task steps or for externally executed processes.

The following table describes the information that is displayed in the Step History panel.

Column	Description
Date/Time	Displays the date and time recorded for the particular status.
Status	Displays each status logged for the step.
User	For webMethods-executed processes that involve webMethods Task Engine for user interaction, identifies the user associated with this step status. For externally executed processes, this column is empty.
Role	For webMethods-executed processes that involve webMethods Task Engine for user interaction, displays the role associated with this step status. For externally executed processes, this column is empty.

The following table describes the information that is displayed in the Control Actions window.

Column	Description
Date/Time	Displays the date and time that the control action was performed.
Action	Identifies the control action taken on the step (suspend, resume, resubmit, or stop).
User	Displays the user associated with the specific control action performed on this step.
Server ID	Identifies the server on which the step executed.

Note:
The Control Actions window appears only when control actions (that is, suspend, resume, resubmit, or stop) have been performed on a step within a webMethods-executed process.

The following table describes the information that is displayed in the Activity Messages window.

Column		Description
Date/Time	Displays the date and time that the activity message was logged.
Entry Type	Displays the type of message.
	Value	Meaning
	Message	The message is informational and no action is needed.
	Warning	The step can complete successfully even if the circumstance causing the warning is not addressed.
	Error	The step cannot complete successfully until the circumstance causing the error is resolved.
Brief Message	Displays a shortened version of the message.
Full Message	Displays the full version of the message.

Note:
The Activity Messages window appears only when a webMethods-executed process step ran a service that logged user-defined messages.

The following table describes the information that is displayed in the Logged Fields window.

Column	Description
Date/Time	Displays the date and time that the custom field was logged.
Field Name	Displays the name of the custom logged field.
Field Value	Displays the value of the custom logged field.

Note:
The Logged Fields window appears only when the process step logged run-time values for certain input, output, and global data document fields. For more information about custom logged fields, see webMethods Monitor User’s Guide.

The Step Errors window displays step errors (either standardized or customized) that have been defined by a user.

The following table describes the information that is displayed in the Step Errors window.

Column	Description
Date/Time	Displays the date and time that the error occurred.
Error Type	Indicates the type of error that occurred. For BAM processes, it displays the name the user gave to the standardized or custom error types for the applicable process instance. See the “Configuring Business Processes” chapter in Administering webMethods Optimize for more information about errors.
Error Message	For BAM process instances, error messages provide the following details based on the category of the error type: For Standardized error types, error messages display details regarding the cause of the error (for timeouts, the time that was expired; for dimension-based timeouts, the dimension instance is listed). For Custom error types, error messages display the error text included in the execution error received from the Monitor API. For System error types, error messages display a detailed message regarding the internal system error that occurred. In some cases, a stack trace is included. This error message matches a similar error message logged to the Analytic Engine's error log file.

4. On the Process Step Detail page, perform any of the actions for BPM processes, as described in the following table.

To	Do this on the Step Information panel
Edit pipeline data for this step	Click Edit Pipeline. For more information, see Resubmitting Processes from a Step and Optionally Editing Pipeline Information. Note: This button is available only for logged webMethods-executed processes that have completed, failed, or stopped.
Resubmit this step	Click Resubmit. For more information, see Resubmitting Processes from a Step and Optionally Editing Pipeline Information. Note: This button is available only for logged processes that have completed, failed, or stopped.