PEGA BA FLOW AND DATA MODELING

Ashock

Flow Modeling

Configure a case step as an assignment, process, or case Model a process using the Process Modeler or process outline Add optional actions or processes to a case Create process flows that comply with flow modeling best

practices

Steps Modeling (Flow)

Steps Modeling (Flow) – Criteria for Choosing Step Type

Flows Modeling – Different Shapes

Intent Driven Design & Flows Best Practices

Optional Process and Local ActionsUser actions allow users to leave the primary path of a case to complete another process. The key is that the user makes the determination to execute the user action; the user action is not automated.

When determining if you need to use a user action, consider the following questions: Should the user be allowed to update the

information at any time during a case or stage? Do you need multiple steps to update the

information? Can the information be updated in a single

screen?

Demo – Instructions, Audit Note , Specification Configure each single-step assignment listed in the following table to include a flow action of the same name, an instruction, and an audit note.

In addition, configure the PTO Request, Extended Leave Request, and Other Leave Request assignments to set the work status to Open.

Demo – Flow Shapes and Connectors– After further discussions with HR we have decomposed the HR Approval and Manager Approval steps

with enough detail to recognize that we need to create a subprocess for each step. Each subprocess should start with an assignment to the manager or the HR department, followed by a decision to determine whether additional approval is needed. If so, the case proceeds to the VP for additional approval. In each flow, if the request is approved, the flow ends, but if the request is rejected, the case shifts to the Reject Request stage.

In addition, we have identified that the following steps should also be reconfigured:

– The Resolve as Approved, Resolve as Withdrawn, and Resolve as Rejected steps do not require any assignments. These flows are only needed to set the status of the case appropriately.

The Notify Requestor of Approval and Notify Requestor of Rejection steps do not require any end user processing. Instead, the flows for these steps should be configured to send an email to the requestor automatically.

Create three new field values for the pyStatusWork property: Open-ResubmittedPending-UpdatePending-Usage

Update the flow rules for the Change Request and Wait for Occurrence steps according to the specifications for each step, and incorporate these three new work status values.

Demo : Work Status

Create a process to allow the requestor to withdraw their time off request. This process should consist of two steps: an assignment for the requestor to document the reason for the withdrawal, and a change to the Resolve as Withdrawn alternate stage. The connector between these two shapes should use the standard Withdraw flow action.

Add the standard pyChangeStage flow action to the Approval and Pending Usage stages.

Demo : Optional Processes and Local Action

Data Modeling

Differentiate between data objects and data elements Identify data objects and elements for an application

Create value-mode and page-mode properties Explain the differences between a page, page list, and page

group Map data entities to properties

Data Modeling

What Data to be Captured

Data Objects Relationships :- ER Diagram creating a data model is to create an entity relationship diagram.This diagram identifies the data objects in an application, the attributes that describe them, and their relationship to each other. It communicates, in a visual manner, the data needs for an application. It guides application developers as they create the data elements, or properties, that store information.

PEGA DATA MODEL – Single Mode

PEGA DATA MODEL – Page Mode

Thank You