Activity form
|
Use these instructions to create activities that can be called directly in flows.
Flow processing automatically controls locking and transaction boundaries for work items. Do not use the Commit method (or the Obj-Save method with the WriteNow parameter selected) in any custom activity called by a flow.
The value of the Activity Type field on the Security tab determines which flow shapes accept this activity. To create an activity for a flow, set the Activity Type field to Utility
, Rule Connect
, Assign
, Notify
, or Router
as appropriate.
First, explore the standard activities of the type you need, as examples and as starting points for your activity.
In all but rare situations, choose a class derived from the Work- base class for the Applies To key part of your activity. This makes your activity available to flows in that class plus all subclasses of the class (subject to security restrictions, rule resolution restrictions and so on).
Assign |
Follow these guidelines and constraints to create an activity of type
|
Integrator
|
Use an Activity Type value of This activity type (and the corresponding Integrator shape) is a reminder that this shape depends on an external system. Response time, availability, and performance may be affected by outside factors. Like the |
Notify
|
Select an Activity Type of Correspondence generation can occur without any user interaction, or can capture user input in a simple HTML form, or may start Microsoft Word on the user desktop. |
Route |
Follow these guidelines to create an activity with Activity Type of
Many routing activities accept these Boolean input parameters:
The standard Routing library (in the Pega-ProCom RuleSet) contains several functions useful in router activities. |
When a flow calls an Integrator
, Utility
, Notify
, or Assign
activity, or another flow, it provides twelve parameters to the activity beyond those declared in the Parameters tab. Click the Show System Parameters button on the Parameters tab to review the names and purpose of the six parameters most often used.
Parameter |
Description |
flowName
|
The subscript of this flow in the work page pxFlow property, a Page Group . |
TaskName
|
The shape name of the shape that this activity or flow was called from, such as SendResolutionEmail or SplitForEach999. |
pyDraftMode
|
True if the flow is in draft mode. |
ReferenceInsKey
|
pzInsKey of the work item page. |
ReferenceClass
|
Class of the work item page (the work type). |
ReferenceInsName
|
pxInsName of the work item page. |
ReferencePageName
|
Clipboard page name of the work item page. |
TimeFlowStarted
|
Date and time that the flow execution began. |
InterestPage
|
Property reference to the embedded page of the work item that is the primary page of the flow. (This is null if the flow's primary page contains the work item.) For example, a flow executing on the Customer work party has an interest page of .pyWorkParty(Customer). |
InterestPageClass
|
Class of the interest page, for example Data-Party. This is an empty string if the flow's primary page is the work item itself. |
FlowHasEnded
|
A Boolean used by internal flow processing to control whether one flow calling another is to wait or to continue. |
flowType
|
Second key part of the flow. |