Types of Activities In Pega

There are 12 types of Activities in Pega. You can choose the activity type in the activity by simply
moving to the security tab. So, let’s check what are the 12 types of activities, why we use them,
when to use them etc.

01. Activity
• Definition: Execute a series of actions or steps in a predefined sequence to achieve a specific
outcome or perform a task within the application.
• Why Use: Used to perform various types of operations such as data manipulation, system
interactions, and business logic execution.
• Scenario: Interacting with external systems or services to retrieve or send data, Implementing
complex business rules or logic that needs to be executed during case processing.

02. Assembler
• Definition: An activity handles the process of combining or formatting data from various sources
or components into a cohesive and usable format, often for presentation or further processing.
• Why Use: Used to construct or assemble data into a desired format or structure.
• Scenario: Combining data from multiple data sources or cases into a single report or view.
03. Assign
• Definition: An activity that creates an assignment, an instance of a concrete class derived from
the Assign- base class. Referenced in a flow to support an assignment. These activities may be
referenced by an assignment shape on the flow.
• Why Use: used to create a work item and assign it to a user or group for processing
• Scenario: Loan Application where a user submits a loan via online.

04. Asynchronous
• Definition: An activity that executes independently of the main process flow, without blocking its
execution.
• Why Use: Used to handle operations that do not need to be completed immediately and helps
improve application performance and user experience.
• Scenario: Calculate a customer's credit score asynchronously to avoid delaying the loan
application process.

05. Load Data Page

• Definition: An activity that explicitly trigger the loading or refreshing of a Data Page.
• Why Use: Used to provide a centralized and efficient way to access data throughout the
application, and the Load Data Page Activity ensures that these data pages are populated with
the most current and relevant data.
• Scenario: Refreshing Data for Real-Time Updates.

06. Notify
• Definition: An activity that send alerts or messages to users or external systems. It helps
automate communication and ensure that relevant parties are informed about specific events,
changes, or actions that require their attention.
• Why Use: Used to alert users about specific events, changes, or actions required within the
application, ensuring that they are informed and can take appropriate actions
• Scenario: Alerting Uses about task assignments.

07. Onchange

• Definition: An activity that executed automatically whenever a specified property value changes,
as defined through a Declare OnChange rule.
• Why Use: Used to handle dynamic updates, perform calculations, or trigger actions in response
to changes in data within the user interface or forms.
• Scenario: Dynamic Field Updates
08. Route
• Definition: An activity that determines which user worklist or workbasket receives an
assignment. In a flow, such activities may be referenced in the Properties panel for an
assignment.
• Why Use: Improve workflow efficiency and case management, ensuring that cases are directed
to the appropriate users or queues.
• Scenario: Assigning Cases to Users.

09. Rule Connect

• Definition: An activity that calls a Rule-Connect external system interface. These activities may
be referenced by an Integrator shape in flow.
• Why Use: Used to communicate with external systems, retrieve data, send data, or perform
operations based on interactions with external resources.
• Scenario: Integrate with a external database.

10. Trigger
• Definition: An activity that starts automatically when an object of a certain class is saved, as
defined through a Declare Trigger rule. Trigger activities are executed in response to specific
events, such as a data change, a case creation, or a timer expiration. They are configured
declaratively, making them easier to maintain and understand.
• Why Use: Can be used to start new processes, invoke other activities, or perform specific actions
in response to certain conditions.
• Scenario: Used to initiate a new case or subprocess based on the outcome of a previous step.

11. Validate
• Definition: An activity that is used to perform validation checks on data or process elements to
ensure that they meet certain criteria or standards before proceeding further in a workflow or
process.
• Why Use: Ensure data integrity, enforce business rules, and maintain the consistency of the
application.
• Scenario: Form Data Validation

12. Utility
• Definition: An activity that typically updates a work item and is referenced in a flow, but requires
no user interaction.
• Why Use: Used to limit manual interactions.
• Scenario: Schedule Notification
Key Points:
✓ When selecting other activity types other than activity in the parameter tab you will get a new
tab called “System-supplied parameters” with the values flowname, flowType,
ReferencePageName, ReferenceClass, ReferenceInsKey, pyDraftMode.
✓ Assembler activity type is currently deprecated.
✓ The Assign, Connect, Route, Notify and Utility types identify activities that are directly
referenced in flows. Typically, activities used in flows have a class derived from the Work- base
class as the Applies To portion of their key.
✓ The Activity Type field on the Activity form corresponds to the property Rule-Obj-
Property.pyActivityType.