Atlas — Standard Flow rules

Your system includes dozens of standard flow rules for your use or tailoring. This table identifies some standard flows that you can reference, or copy and modify.

To start execution of a standard flow, a user must hold either the standard privilege AllFlows or a standard privilege named FlowZzzzz, where Zzzzz is the name of the standard flow. Except for the guest access role role, the standard access roles all provide access to the AllFlows privilege.

Use the Rules by Type Explorer to see a complete list of the standard and custom flows available to you, based on your RuleSet list and security.

Flows in the Work- base class

Flow rule	Purpose
BPMN	Template rule for flow rules that use BPMN notation.
ConnectionProblem	Supports notification, retries, and repair of connector tasks in flow executions. See Handling connector exceptions.
EngageExternal Information, EngageExternal Quick	Implements the directed Web access feature.
FeedbackDiscussion	Completes a request sent by one user for advice or assistance. Part of the standard flow Work-.RequestAssistance, that supports a form of peer-to-peer collaboration.
FinishPolicyOverride	Support review of suspended work objects. See Understanding policy overrides and suspended work objects.
FixCorrespondence	Supports detection and routing of failed correspondence. See Understanding the Pega-ProCom agent.
FixWork	Supports resolution of flow problems by an administrator.
FlowProblems	Creates an assignment for a designated operator who is to address problem flows. Your flow rules can start this flow (identifying the assignee as a parameter) if they detect a flow problem, a situation suggesting incorrect or incomplete configuration, that requires attention. See flow problems.
NewWork	Creates a work object, makes one assignment, and adds a confirmation note attachment.
Notify	Allows generation of correspondence; the user can select one correspondence rule from a list. Can be called as a subflow.
RequestAssistance	Supports collaboration among application users by allowing them to create discussion thread, captured as a sequence of note attachments. See collaboration flow.
SendCorrespondence	Sends correspondence that requires verification by a supervisor.
StandardParallelWork	Provides an example of Split/Join processing.
VerifySendCorr	Sends correspondence that requires verification by a supervisor.

Flows in classes derived from Work-

Flow rule	Purpose
Work-Cover-. NewWork	A flow for a cover object, enforcing a requirement that the cover object cannot be resolved until all of its associated covered work objects are resolved.
Work-Folder-. NewWork	A basic flow for a folder work object.
PegaSample-. QualifyScanned Documents	Supports an operator who examines scanned document images (acquired through the Scan Station tool) and qualifies the work objects. Part of the PegaSample sample application. This flow requires a workbasket named ScannedDocuments@organization, where organization is the key to the Organization data instance associated with the operator using the flow. See Scan Station tool.
PegaSample-CustomerRequest-.NewWork	A flow in the PegaSample sample application that demonstrates covers.
PegaSample-CustomerRequest-.CustomerFeedback	A flow in the PegaSample sample application that demonstrates a screen flow.
PegaSample-Folder. NewWork	A flow in the PegaSample sample application that demonstrates navigating a folder.
PegaSample-Task.Word-EmbedMergeTest	A flow in the PegaSample sample application that demonstrates inline Word editing.
PegaSample-Task.SimpleProcess	A simple flow in the PegaSample sample application.

About Flow rules
Atlas home