Process and Rules category — Processes page

The Process Explorer gadget displays in a graphical form — for the current application and selected work pool — starter flow rules and the subflows they call. This makes it easier to identify caller/calling relationships among flow rules in an application.

1. Select By Description? to present Short Description text within the rectangle that displays each flow rule. Clear this checkbox to present the Flow Type key part instead.
2. Starter flows — those that create new work objects — appear as green rectangles at the left of the display (). Subflows (called, branched to or referenced by a Split-Join or Split-ForEach shape) appear beneath and to the right of flows () as blue rectangles.
3. A large application may contain many levels of subflows. Adjust the Levels control to determine how many levels are presented. BUG-3167
4. Click any rectangle to open the corresponding flow rule.

Notes

• Your Internet Explorer browser must include a Flash 9 or higher plug-in from Adobe Systems to use the Process Explorer. See How to set up Internet Explorer 7.
• One flow may be called or branched to by multiple subflows, and may appear at more than one level.
• The display includes flow rules in the RuleSet and version of the class rule that corresponds to the current work pool. This includes rules that appear above that RuleSet on your RuleSet list, if the RuleSet instance lists the RuleSet as a prerequisite.
• Flows in your private RuleSet do not appear. Orphan flow rules that do not create a work object and are not referenced as a subflow by others do not appear.

This report lists flow errors that are routed to your worklist or work group in your current application by a getProblemFlowOperator activity. Each row identifies one flow problem. Rows may reflect a common condition or unrelated conditions from multiple applications.

Using the View errors located in drop-down list, select Worklist or Workbaskets to see flow errors that are routed to one or the other in your current application.

Column	Description
Add	Select to designate one or more rows that you want to apply your problem resolution choice as defined by the button you select on this gadget.
Error Message	Underlying problem that caused the flow error.
ID	Identifier of work object associated with this error.
Flow	Name of the flow in which the error occurred. To open the flow rule, click the displayed name.
Step	Name of the problem flow step in which the error occurred (pyFlowParameters.ProblemFlowStep).
Operator	ID of operator to whose worklist the problem flow assignment is routed by the getProblemFlowOperator activity. To open the Operator ID rule, click the displayed name.

After you have diagnosed and addressed a problem, check the Add box in one or more rows of this report and click a button to implement your disposition of the problem.

Button	Result
Refresh	Updates this report with the latest list of flow problems on your worklist.
Select All	Selects the Add box for every row in the report.
Deselect All	Clears the Add box for every row in the report.
Resume Flow	Click to resume flow execution beginning at the step after the step that paused, without re-executing any rule in the step that paused. This choice is common after many types of repairs to rules or data objects. For example, if a flow is stuck at a Decision shape, you can either: MARIK 3/17/06 Update the flow rule to add a missing connector and click  Resume Flow. Update the decision tree, decision table, or map value rule to return a value that the flow already accepts, and click Retry Last Step.
Retry Last Step	Click to resume flow execution but begin by re-executing the step that paused. This choice is typically appropriate for connector failures or timeouts.
Restart Flow	Click to start flow at the initial step.
Delete Orphan Assignments	Deletes an assignment for which the work object cannot be found. Such orphans may arise through design or implementation errors, access issues, RuleSet issues, or database integrity issues.

About flow errors

When it detects a flow error, Process Commander normally starts the standard flow Work-.FlowProblems (using the same work object ID). It creates an assignment and places the assignment on a worklist, typically named administrator@zzz.com, where zzz.com is the organization of the operator who last worked on the work object. You can customize the standard activity Work-.getProblemFlowOperator in each application to send these to a different worklist or to a workbasket.

For example, these conditions cause a flow error execution to start:

• The flow rule references a rule that does not exist, or a rule that the user (or agent) executing the flow lacks RuleSets, versions, access roles, privileges, or other prerequisites to execute. Examples: an activity, service level, decision tree, harness, map value, or subflows.
• The flow rule references a data instance that does not exist. Examples: workbasket, operator, organization, work group, access group.
• The flow execution is stuck, in that following a decision shape, none of the outgoing connectors evaluate to true.
• An activity has failed, or a connector rule has failed or timed out.
• The work object contains invalid data that causes one of the above conditions.
• The database, hardware, network, or system software has failed.

In a production setting, review and diagnose every flow problem or problem assignment to insure data integrity.

Use this gadget to verify which service level agreements (service level rules) are in active use, and by which flows, in the current application.

Column	Description
Name	Name key for this service. To open its rule form for review or updating, click the displayed name.
Applies To	Class key for this service. To open the class form for review or updating, click the displayed name.
Goal	The Goal value defined on the General tab of the service level rule.
Deadline	The Deadline value defined on the General tab of the service level rule.
References	The count of flow rules with assignments that reference this service level rule. Double-click the number to display a list of flows that comprise the total.