Process and Rules category — Processes page

The Process Explorer tab displays in a graphical form — for the current application and selected work pool — starter processes and the subprocesses they call. This makes it easier to identify caller/calling relationships among the flows in your application.

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

• Your Internet Explorer browser must include a Adobe Flash 10 or higher plug-in to use the Process Explorer. See How to set up Internet Explorer 9.
• One flow may be called or branched to by multiple subprocesses, and may appear at more than one level.
• The display includes flows 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 personal RuleSet do not appear. Orphan flows that do not create a work item and are not referenced as a subprocess 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.

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.

About flow errors

When it detects a flow error, PRPC normally starts the standard flow Work-.FlowProblems (using the same work item 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 item. 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 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 subprocess.
• The flow 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 item 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 the SLA tab to verify which assignment and work item service level agreements (service level rules) are used, and by which flows, in the current application.

This Status Values tab provides a single place to view all of the work item status values currently defined and available in the system. The values, such as New, Open, and Resolved, indicate a case's progress as it moves through its business cycle.

To view or modify a work status, open

This report lists the standard activities, flows, and flow actions ( collectively known as the Process API) that you can use to start and advance flows without implementing user forms. These rules can support BPM processing through Service Oriented Architecture (SOA) facilities including agents and service activities.

Business process management applications can use an external portal or external system and call PRPC services that in turn call Process API rules to create work items, advance the work items through a flow, perform assignments, and so on. You can also use these in certain places within browser-based, interactive applications, or without user forms in headless applications or straight-thru-processing.

For more information about API activities, see Atlas — Process API.

This display is also available from the help menu. Select > APIs > Process to open the APIs tab.

Column	Description
	Click the expand icon in the row header to learn more about each activity, flow, or flow action. Information includes the rule's parameters (except flow actions).
Rule Name	The Activity, Flow Name, or Action Name key part of the activity, flow, or flow action, respectively. Click the name to open the rule form.
Category	The name of the rule type (activity, flow, or flow action).
Description	A short summary of the rule's purpose.
Applies To	The Applies To class of the rule.
References	The number of rules in the system that reference this API rule. Click the value to open the Referencing Rules display.