Back Forward About Flow rules
 

Process category
  1. About
  2. New
  3. tab1
  4. tab2
  5. tab3
  6. tab4
  7. tab5
  8. History
  9. More...
New Diagram Parameters Pages & Classes
Design Process Use Cases Requirements
Test Cases History More...

  Show all 

Purpose

A flow rule defines a business process or part of a business process. A flow rule governs how work objects are created, progress through the system, and become resolved. A flow rule consists of a network of shapes and connectors (lines), each with associated parameters and values.

Flows are the fundamental rules that represent business processes. They determine who works on a work object in what sequence, what decisions and processing occur automatically, and other aspects of the business process.

After you complete and save the flow form, click the Run toolbar button (Run) to create a new work object with the flow. (The Run toolbar button is visible only for starter flows — flows with Creates a new work object? selected on the Process tab.)

Use the Process tab to constrain which users can execute this flow. Use the Parameters tab to identify flow parameters to be supplied when a flow execution starts. Use the Diagram tab to explore a flow rule interactively and preview the rules it references, including the runtime appearance of work object forms.

  Editing with the Process Modeler

XXXXXXX: See XXXXX TEMPORARY XXXXXXX

  Shapes and Visio editing

Click the Flow Editor toolbar button (Flow Editor) to start Microsoft Visio and edit the flow. If Visio presents a warning about macros, select the choice to trust the publisher (source). (See How to set up Visio.)

Click the Return button (Return) when you complete Visio editing.

To change the shape properties of an existing shape, but not alter the structure and relationships among shapes, access the Design tab, right-click a shape, and select the Edit tab.

As a best practice, ensure that everyone in your development team is using a common version of Visio. Process Commander operates identically for Visio versions 2003 and higher. However, when you save a flow rule edited with one version of Visio, that rule cannot later be edited using a lower version.

Tip Flow rules containing too many shapes can introduce complex, difficult-to-debug processing into your application. As a best practice, guardrails recommend limiting a flow rule to contain 15 or fewer shapes, not counting Notify and Router shapes. If your flow grows to contain more than 15 shapes, revise the flow to call or branch to subflows to handle continuations, special cases, or non-mainstream processing.

These topics describe aspects of flow editing:

  Visio editing basics   Screen flow rules
Flow properties
notify shape
Notification shapes
Comment
Start shape
Router
Router shapes
Assignment symbol
Assignment shapes   Service levels
Assignment-Service shapes image/img00081.gif Spin-off shapes
Comment
Comment shapes
Split Join shape
Split-Join shapes
connector
Connectors and flow actions
Split for Each
Split-ForEach shapes
Decision shapes
Swimlane
Call or branch to subflow shape
ticket shape
Ticket shapes
FlowEnd
FlowEnd shapes
Utility shape
Utility shapes
Fork
Fork shapes Using freeform shapes and other stencils
Integrator shapes   Building a flow rule from an external flow diagram

  Delegation

C-494 KHATV 10/22/03 After you complete initial development and testing, you can delegate selected flow rules to line business managers. The Diagram tab of the Flow form provides managers with access to the fields most often updated.

TipFor each flow rule in your application, consider which business changes might require rule updates, and whether to delegate the rule to non-developers who then can make such updates directly. See How to build for change.

  Access

Select > Process & Rules > Processes > Process Explorer to display the flow rules in the current application. See Process & Rules category — Processes landing page.

Use the Rules Explorer to list all the flow rules available to use.

  Additional development steps

TipDefining a flow rule that creates new work objects does not automatically make the new flow rule available from the portal. For step-by-step instructions, see How to create a flow and make it available.

 Category and database table

Flow rules are part of the Process category. A flow rule is an instance of the Rule-Obj-Flow rule type.

Flow rules are normally stored in the PegaRULES database as rows of the pr4_rule_flow table.

Related topics Debugging with the Tracer    
Flows — Concepts and terms
How to create an activity for use in flows

Understanding transactions in flow executions
How to unit test a flow rule
Standard rules Atlas — Standard flows
Atlas — Standard activities for flows

Process category
Help System home pageHelp Home