Creating an Application IN PEGA

PDN Access only for the licenced users.

PEGA Guard rails are to be followed

Object oriented principles and inheritance. Rule Sets

Direct Capturing Objectives - tools available to generate the applications

User name - Operator Id- has a default access group to one applications, also can have multiple AG.

Operator - Access Group - Application - Rulesets.

Application Details Tab defines Work types, Use cases, Actors

Application Requirements

Application Associations

Application Advance feature is password protected, to prevent others from changing the definition

Rulesets are container for all rules. In production, rulesets are in locked state, to edit a ruleset we create a
new version.

Version - Major- Minor- Patch...

Version if at major tree 01-01 then all the patch are included. But if the version says 01-01-10. any patch
above 10 is excluded. Rules Resolutions is another topic.

pxObjClass or RULETYPE is the name of the class. In the xml file you have name value pair and
pxObjClass for access group, application can be found in the xml file as follows.

< pxObjClass>Data-Admin-Access Group</<pxObjClass>>

< pxObjClass>Rule-Application</<pxObjClass>

Applies to - Scope of the particular rule.

Workpool is set of worktypes . In the Application Explorer you have all work types(by the scope)

Application Explorer Categories Tree structure

I--Applies To
I-------------Category Class - User Interface

I-----------RuleTypes pxObjClass - Sections

I--------- Rules instances of class

1. Properties

2. Process - Rule

3. User interface - Sectiom

4. SysAdminn - Ruleset

A starter flow rule is one that creates new work objects , workobject is an instance, it has an unique id.
Users identify a work type as they enter each new work object. A work type is any concrete class derived
from the Work- base class. The set of all work types available to them is determined by the Class Group
entries in their access group. A work type label is derived from the Short Description on the Flow form, for
a start flow rule (with that work type as the Applies To key part). Workpool is set of worktypes.

Enduser has workobject id in the database.

Create an application

1. Click the Landing pages, then Org&Security - Organization- Organization Setup

This will create the initial rule instances to be used in the system.

The initial rules will all be derived from the organization name provided.

Please print this screen after the organization name has been provided as this information will be

used to initially sign onto the application. NOTE: Organization Name may only consist of 2 or more

alpha/numeric characters starting with Alpha. No special characters or blanks allowed.

Organization Name : nayana Action: Create

Please review the changes that were made to the application. You may wish to print this page as a
reference. You should sign off the system and sign on using one of the users that were created to begin
configuration.

Top Level Class: nayana-

Organization: nayana.com

Organization Division: nayanaDiv

Organization Unit: nayanaUnit

RuleSet Name: nayana

Application Name: nayanaApp

WorkGroup Name: default@nayana.com

WorkBasket Name: default@nayana.com

Users Created: Administrator@nayana.com

SystemArchitect@nayana.com

BusinessAnalyst@nayana.com

Manager@nayana.com

User@nayana.com

2. Login using one of the Created User

You will get a default screen.

3. Create an Application - Give the name of CarPurchase Application

It ends in a Flow called StartCarPurchase(Start + "WorkType")

A flow rule — an instance of the Rule-Obj-Flow pxObjClass or rule type — is a network of shapes

representing tasks and connectors (directed arrows), each with associated parameters and values. Flows
govern:

 How work objects are created

 How they progress through one or more flow executions

 How they become resolved (completed)

Flows are the fundamental rule instances that represent business processes, identifying who works on a
work object in what sequence, what decisions and processing occur automatically, and many other aspects
of the business process.
Some applications don't require users to interact with work object forms. Flows that implement straight-
through-processing operate without user input.
4. Create a flow, Click the Blocks for Use cases, fill the Description, Requirement

Building Application creates the following

RuleSets 
Organization Records 
Classes 
Application 
Use Cases 
Models 
Parties 
User Interfaces 
Flows 
Access Groups 
Use Case and Requirement References 

4. Create a flow, Click the Blocks for Use cases, fill the Description, Requirement

5. Define the actors

6. DCO then creates the applications. It creates implementation layer and framework

Enterprise Level Structure is as follows

All application is built on PEGARules. Then Framework - Implementation Layer - Organization(MICO) -

Division(MICO SALES)

*** Busines Objective is different from Requirements

Puchase a car Application using Application Accelerator

Homework
Create app using accelrator

Sysadmin-class rule form

Go through the PDF.

1. Create a new Organization

2. Logout - log back back in using Businessuser id, paswd rules, Create in application
3.Create the rules
4. create the actors.
5.create application( creates a default rulesets)
6.Edit the Sections. Add welcome screen. Add Data Entry
7. Create property. Define properties in bulk.
8. Associate the properties to UI text boxes
9. Preview the section..
10, Run the flow( Process --> Flow--> Run). Harness comes into picture and we can see all the UI
elements.
11. Open Visio. Assigmnments are like Pause, as application waits for user input.
Connectors flowing out of Assignments is called FlowActions. Likelihood. FlowActions have the sections
too, hence called a wrapper too.
Create Section, create flow action. connect flowaction to section( choose purpose)

Flow is nothing but a process. Flow is set of usecase

Sections dont exist by themselves, they need harness.

What PEGA guard rails. in certification no more than 25 activity

Starter Flow - Flow creates a new work object

Sub Flow - only called by Starter flow

Technical - Activities copies from one section to another section