Pega – Platform and an interface to build web applications end to end. A BPM product.

It’s a tool built

on Java.

PRPC – PegaRules Process Commander. PegaRules – Rule Engine

Process Commander, which is a layer of pre-configured rules that are designed to provide a solid
foundation to enable rapid onward development and customization in order to create applications to
fulfil the needs to the diverse client base using the technology (BPM)

BPM – Business Process Management.

administrator@pega.com/install

Dev/App/Admin/Prediction Studio’s available.

Dev – Developers

App – BA’s to design the flows and draft workflows by Business

Admin – Administrators who manage app server, DB, installation, load balancer, configurations, patches
etc

Prediction – Data Analytics

Pega best practices:

https://docs.pega.com/implementation-methodology-and-dco/ten-guardrails-success

Enterprise Class Structure (Organizational->Division->Framework->Implementation layers)

Class Types: Concrete and Abstract Types

Concrete -> Can have work objects created under them

Abstract->cannot have work objects created under them

Work Object: Instance of a class.

Inheritance – Reusing rules from parent class.

Types of Inheritance – Pattern and Directed inheritance.

CaseType -> Stage (Primary/Alternative Stages) ->Flow->Steps

Can have max 9 stages and have no limit on flows.

CaseType – from settings can define the format of these type of cases and if we prefer to auto number
by default, along with setting a priority (0-100)

Types of flows:

Process Flow Screen Flow

 one-way only forward navigation  bi-directional navigation
 No Tree Navigation  Tree Navigation
 Routing  No Routing
 Integration  No integration
 Case creation possible  Case creation can’t happen
 Few smart shapes not available like
1. split join
2. spin off

User Interface:

Portal – web page with user experience

Harness – Page Layouts
Section – UI Container with UI Controls. Multiple Sections in a Harness based on layout
chosen.

Flow action – It is triggered from a flow (case type flow). Steps are flow actions. Can contain only one
section with ui controls and create work objects to persist data.
 Section – Flow action can have only one section.
Layouts – Table like structures to keep content

Harness Types:

New – Used when a new case (work object) is created. It is the 1st screen that appears on case creation.
Perform – This allows a user to perform action on a screen.
Review – Read only mode
Confirm – Confirmation messages.
Flow action types:
Local action – Flow action triggered from a button/hyper link, displayed like a popup or an optional
action.
Connector Flow action – flow action triggered from a flow connector (following regular flow sequence)

talluri@ftr.com/rules created for ftr custom application.

Data.pr_data_admin is where all access groups are stored.

Data.pr_operators is where we store all operators/users.

Implementation layer - Organization Name + ‘ – ‘ + Application Name

App explorer – Classes