Viewing Process Instance Details

To view details for a process instance

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

2. Search for the process you want to work with.

3. Click the Instance Detail icon (

) that appears in the Detail column in the Process Instances panel on the Process Instances page.

Optimize displays the Process Instance Detail page, which displays the most important information about a process instance. It offers the following buttons:

Previous and Next. These buttons enable you to move through the process instances listed in the search results without having to return to the Process Instances page.

Refresh. Updates the page with the most recent process data available.

Close. Closes the Process Instance Detail page and returns to the Process Instances page.

The Process Instance Detail page contains the information listed in the following tables.

The following table provides information about the Process Instance Information panel.

Field	Description
Process	Displays the name of the business process associated with the selected process instance.
Model Version	For a webMethods-executed process, this indicates the version of the process model assigned by Software AG Designer. For an externally executed process, this will display “N/A.”
Start Date/Time	Indicates the date and time that the selected process instance started.
Last Updated	Indicates the date and time that Optimize last updated the selected process instance.
Instance ID	Displays the unique identifier for the process instance. If a process instance ID consists of multiple parts (such as order numbers from two or more different order systems), Optimize creates one row for each part of the process instance ID.
<Process-specific columns>	For processes that contain custom information, Optimize displays process-specific custom columns when you select a single webMethods process to view. If multiple processes are displayed, the contents of these custom columns are concatenated within the Process Instance ID. For more information about custom columns, see Dynamically Generated Custom Columns.
Parent Instance ID	Unique identifier for the parent process instance, if applicable. Provided only for instances that have been started by other instances.
Instance Iteration	Indicates the number of times the process instance was submitted.
Status	Indicates the status of the process instance, as described in Using the Analytics Overview Page in this guide.
Duration	For active process instances (those with a status of Started, Resumed, or Resubmitted), duration represents the length of time that this process instance has been executing, calculated by subtracting the start time of the process from the current system time. For inactive process instances (those with a status of Stopped, Completed, Failed, or Suspended), duration represents the length of time that the process instance was active, calculated by subtracting the start time of the process from the time the process became inactive. For process instances that have timed out (status of either Stopped or Completed) or have been canceled (status of Stopped), duration represents the length of time that the process instance was active, calculated by subtracting the start time of the process from the time the cancel or timeout action occurred. Note: For process instance steps that execute in parallel, this Duration value does not include the overlapping execution time.
Buttons:	These buttons are available only when a process instance is running (that is, does not have a status of Completed). Update. Available when a process instance is running and a new version of the source process model has been enabled. This updates the running instance so that it uses the newly enabled model version for the rest of the process. Suspend/Resume. Click to suspend or resume a process instance. Stop. Click to stop the process instance.

The following table provides information about the Process Stage Timeline panel.

Process Stage Timeline Information

The Process Stage Timeline panel displays a graphical presentation of stage activity and status over time. webMethods Optimize for Process must be installed to be able to view stage timeline information.

Note:
When a process contains no stages, or if webMethods Optimize for Process is not installed, this window is collapsed to show only the title bar. It cannot be expanded.

Note:
Process stage logging does not occur instantaneously. This can result in a delay of up to five minutes between stage instance changes and the stage status displayed in the Stage Timeline window. For example, when viewing a recently executed process instance, stages may initially appear as not yet started. Click the Refresh button on the Process Instance Detail page to update the Stage Timeline window. For more information, see “About Process Generation and Stage Status Display” in the Building and Uploading chapter of webMethods BPM Process Development Help.

By default, stages of all statuses are displayed, as indicated by the stage status display check boxes:

You can filter the list of displayed stages by clearing a stage status check box, which removes stages of that status from the display. Select a check box to display stages of that status. The stage list provides the following information:

Note:
Click on a column name to activate the sort controls for that column.

The following table provides information about the columns of the Process Instance Information panel.

Column	Description
Status	The current status of the stage: Completed, Running, Incomplete, or Not Started.
Name	The name assigned to the stage.
Cycle Time	Cycle time is based on the status of the stage: Completed. The length of time it took for the stage to run from start to completion. Running. The length of time since the stage began executing. Incomplete. The length of time it took for the stage to run from start to the time it stopped running for any reason other than completion (for example, step failure or process suspended). Note: A stage will have incomplete status: if it is still running when the process terminates for any reason. This can happen with normal process execution if the process instance took a split branch that does not terminate. if the End Milestone of a stage is defined as the start or end of a step which is part of a subprocess. Not Started. No cycle time is displayed.
Deviation	Deviation is calculated only when the stage is breached. A value of +/- 0 indicates no deviation. A stage that has breached its defined condition is indicated by an alarm icon . The deviation time is calculated by comparing the Cycle Time to the Condition expression defined for the stage. If the condition specifies <, then the stage is breached when the cycle time exceeds the specified time period. If the condition specifies >, then the stage is breached when the cycle time is less than the specified time period. For example: If the Condition expression is “< 2 seconds” and the stage completes in 3 seconds, the deviation is 1 second, and the stage is breached. If the Condition expression is “> 2 hours” and the stage completes in 1 hour and 30 minutes, the deviation is -30 minutes, and the stage is breached.

You can obtain additional stage information as follows:

Hover the cursor over any row in the stage list, or over the colored bar for a stage in chart area to view the stage name and description as well as the following:

Status: The current status of the stage.

Start Milestone: The point in the process where the stage starts.

End Milestone: The point in the process where the stage ends.

SLA Condition: The expected execution time specified in the stage’s Condition expression.

Stop Tracking On Breach: Indicates if this option is selected (Yes or No).

Clicking any row in the stage list does all of the following:

Displays the stage’s start milestone Start Milestone icon

and stage end milestone End Milestone icon

in the Process Diagram window. Only one stage can be displayed in the Process Diagram at any time. Click another row to display the milestones for another stage.

If you have selected the Stop Tracking On Breach check box for a stage and that stage experiences a breach, all stage tracking ceases and any remaining stages in the process are marked as Incomplete. In this case, it is possible for the steps within the stage to be shown as Complete in the process diagram, while the stage that contains them is shown as Incomplete. This is expected behavior.

Filters the Step Summary list to display only those steps that executed within the stage's cycle time. Steps that are in a different path from the stage's start and end milestone steps will also be included if the step’s execution time falls within the stage cycle time.

Filters the Logged Fields list to display only those logged fields that belong to a step in the filtered Step Summary list.

Click Clear Selection in the Process Stage Timeline window to remove the milestone icons and display all process steps in the Step Summary window and all logged fields in the Logged Fields window.

To set the time resolution for the chart, select from Year, Month, Week, Day, Hour, or Minute in the Time Unit list.

The Process diagram depicts the progression of steps in the process. If the process is a webMethods-executed process, status icons appear on the steps in the diagram.

The following table provides more information about the status icons for webMethods-executed processes.

Icon	Description
	The step is running.
	The step has completed.
	The step has failed.
	The step is waiting (for example, to receive an external document).

In addition, you can display milestones for an individual stage by selecting the stage in the list portion of the Process Stage Timeline window. See “Process Stage Timeline”, above, for more information. The following right-click options are available for process diagrams on the Process Diagram panel.

Fit to screen - Resizes and re-centers the diagram based on the screen size.

Hide transition labels - Hides description and expression text on all transition lines in the diagram.

Show transition descriptions - Shows all applicable description text created in Designer for all transitions on the diagram.

Show transition expressions - Shows applicable transition expressions created in Designer for all transitions on the diagram.

Note:
External (BAM-only) processes can have only one status: “The step has Completed.” No other statuses listed here are displayed for these processes.

The Step Summary panel displays information about the execution of the steps within the process instance.

Note:
The list of steps can be filtered by stage by selecting the stage in the list portion of the Process Stage Timeline panel. See “Process Stage Timeline”, above, for more information. Click Clear Selection in the Process Stage Timeline panel to display all process steps in the Step Summary panel.

The following table provides information about the panel.

Column	Description
<Status Icons>		The step started successfully. The step has started and may include errors. The step completed with errors.
Step Name	Displays the name of the step.
Start Date/Time	Indicates the date and time that the step began executing.
Last Updated	Indicates the date and time that the step stopped executing.
Instance Iteration	For webMethods-executed processes or workflows, identifies the number of times the process or workflow executed, including re-submissions. For externally executed processes, this value will always be 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.
	Value	Meaning
	Started	The step has started. The step may be executing with errors.
	Stopped	The step was canceled. This status is not applicable to BAM-only processes.
	Completed	Either the step completed successfully or the step completed but it executed with errors.
	Failed	Either the step stopped because it executed with errors or the step is no longer being tracked and is missing information. This status is not applicable to BAM-only processes.
	Expired	The time specified for the step in the process model for an event to occur expired before the event was satisfied. For example, the time set for a join condition expired before a document required by the join condition arrived.
	Retries Exceeded	An attempt was made to execute the step more times than is specified.
	Unsatisfied Join	A join definition for the step has not been satisfied. That is, some incoming transitions have not arrived.
	Waiting	Step is waiting for an event to occur (for example, the step might be waiting for a document to arrive).
	Interrupted	The step has been interrupted by an interrupting boundary event.
Duration	For active steps (those with a status of Started), duration represents the length of time that this step has been executing, calculated by subtracting the start time of the step from the current system time. For inactive steps (those with a status of Stopped, Completed, or Failed), duration represents the length of time that the step was active, calculated by subtracting the start time of the step from the time the step became inactive. For steps that have timed out (status of either Stopped or Completed) or have been canceled (status of Stopped), duration represents the length of time that the step was active, calculated by subtracting the start time of the step from the time the cancel or timeout action occurred.
Referenced Processes	webMethods-referenced process or BPMN callable process that was executed at run time for this step.
Detail	Displays the KPI Detail icon and the Step Detail icon. Click either icon to view more details about the step execution.

The Control Actions panel appears only when a control action (suspend, resume, resubmit, or stop) has been performed on a webMethods-executed process. This panel is available only for BPM processes.

The following table provides information about the Control Actions panel.

Column	Description
Date/Time	Displays the date and time that the control action was performed.
Action	Identifies the action taken on the process instance (suspend, resume, resubmit, or stop).
Instance Iteration	Displays the process iteration upon which the control action was taken.
Step Name	Displays the name of the step, if applicable.
Step Iteration	Displays the step iteration upon which the control action was taken.
Server ID	Identifies the server on which the process instance executed.
User	Identifies the user associated with the control action.

The Activity Messages panel appears only when a webMethods-executed process executed a service that logged user-defined messages. This panel is available only for BPM processes.

The following table provides information about the Activity Messages panel.

Column	Description
Date/Time	Displays the date and time that the activity message was logged.
Step Name	Displays the name of the step.
Entry Type	Displays the type of message.
	Value	Meaning
	Message	The message is informational and no action is needed.
	Warning	The process can complete successfully even if the circumstance causing the warning is not addressed.
	Error	The process 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.

The Logged Fields panel appears only when the process has logged run-time values for certain input, output, and global data document fields. For more information about custom logged fields, see the webMethods BPM Process Development Help.

The following table provides information about the Logged Fields panel.

Column	Description
Date/Time	Displays the date and time that the custom field was logged.
Step Name	Displays the name of the step.
Instance Iteration	For webMethods-executed processes or workflows, identifies the number of times that the process or workflow executed, including re-submissions. For externally executed processes, this value will always be 1.
Step Iteration	Displays the step iteration that was executing when the custom field was logged.
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.
Input/Output	Indicates whether the logged field was defined to log from the step input pipeline or the step output pipeline.
Field Name	Displays the name of the custom logged field.
Field Value	Displays the value of the custom logged field.

The Process Errors panel displays information about process errors and step errors, sorted by time. Note that some fields are specific to either BAM or BPM processes.

The following table provides information about the Process Errors panel.

Column	Description
Date/Time	Indicates the date and time that the error occurred.
Error	This column is empty for BPM processes. 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.
Message Detail	This field is applicable only to BPM processes. It provides additional run-time error text and, where applicable, a stack trace with details about the error.
Service Name	Displays the name of the webMethods service that was invoked when the error occurred. This column appears only when a webMethods service is associated with the error. This field is applicable only to BPM processes.
Step Iteration	Number of times the step was executed as a result of: A transition drawn to this step downstream step that causes the step to execute multiple times during a single process execution. The process was resubmitted, causing the step to execute again.
Step Name	Displays the name of the step that was executing when errors occurred and lists all related errors. This field is empty for errors at a process level, such as a process timeout.
Server ID	Identifies the server on which the error occurred. This column appears only if a specific server is associated with the error. This field is applicable only to BPM processes.

4. If you want to see more details about the execution of a particular step, click the Step Detail icon (

) next to that step in the Step Summary panel and continue to Process Instance Step Details.

5. If you want to resubmit a step, see About Resubmitting Process Instances and Process Steps and Resubmitting Processes from a Step and Optionally Editing Pipeline Information.