Back Forward Help: Working with the Flows with Problems report

 -- Show all 

A problem flow execution (or problem flow for short) is a list report of a paused flow rule execution for a work object. A problem flow can be caused by many different conditions, relating to the flow rule, the properties in the work object, capabilities of users, and other data.

After you determine the cause of the problem flow and make any needed changes, you (or the user who has the assignment) may be able to resume execution.

zzz Which reports can I view?

Problem flow and problem assignment list reports are organized into two categories: workbasket and worklist. You access them by selecting View > System > Flow Errors (or Assignment Errors) > In Worklists... (or In Workbaskets...) from the dashboard menu. The next step in the selection tree enables you to choose a list report that contains all errors within the operator's application, or those within the operator's organization, division, or business unit. You filter the choices available by using privilegesReconcileProblemWork, ReconcileProblemWork_Organization, _OrgDiv, and _ OrgUnit in class @baseclass within instances of Rule-Access-Role-Obj.

By default, privilege ReconcileProblemWork is listed in the Access of Role to Object rule for the role PegaRULES:SysAdm4.@baseclass, which enables these operators to view reports that contain all flow and assignment errors. For example, this operator sees View > System > Flow Errors > In Worklists...> All, Current Organization, Current Division, and Current Unit in the menu. The operator can choose to view an all-inclusive report, or view reports filtered by organization, division, and business unit.

You modify individual operator Access of Role to Object rules by adding the appropriate privilege to the rule. For example, operators with ReconcileProblemWork_OrgDiv in their list see Current Division and Current Unit in the menu. Each privilege inherits from the one below. Enter only one privilege at the highest access level you need.

These privileges are also used in the security settings on the Content tab in problem flow and problem assignment list view report rule instances in class Assign-. These list view reports include ProblemAssignments, ProblemFlows, ProblemAsssignmentsForCurrent Organization, ProblemFlowsForCurrentOrganization, and so on. The default privileges in the security settings are based upon the appropriate levels of access. For example, ProblemFlowForCurrentOrgDivision contains all privileges except ReconcileProblemWork_OrgUnit. The list view rule ProblemAssignments has no default security settings.

--Which assignments appear in this display?

When it detects a problem flow, Process Commander by default 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 override the standard routing activity Work-.toProblemFlowOperator in each application to send these to a different worklist or to a workbasket.

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

--Working with problem flows

Flows with Problems — In Worklists

This report lists problem flows routed to your worklist by a getProblemFlowOperator activity. Each row identifies one flow problem. Rows may reflect a common condition or unrelated conditions from multiple applications.

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  

Tries 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:

  • 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 excepts, and click  Retry Last Step  .
Retry Last Step  

Tries to resume flow execution but begin by re-executing the step that paused. This choice is typically appropriate for connector failures or timeouts.

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.

Flows with Problems — In Workbaskets

This report list problem flows routed to workbaskets that you can access. (Such routing may occur when an application has overridden the standard getProblemFlowOperator activity.) This report operates similarly to the Flows with Problems in Worklist report. Follow above instructions.

Flows with Problems — Activities for Flow Problem Operators

Click to review each of the activities in your Process Commander system that process flow problems. Each activity is named getProblemFlowOperator. These activities may belong to different applications.

Definitions flow problem
Related topics Troubleshooting — Stuck work objects

-- Developer portal basics