Configuring application settings in the New Application wizard

On the Application settings form of the New Application wizard, you can select a built-on application,
control how many class layers are generated, and define other relevant settings for your new
application. You work with this form as the first step in creating an enterprise application.

To configure your application settings:

1. In the Application name field, enter a unique name that starts with a letter and can contain
alphanumeric characters, ampersands, underscores, or hyphens.

Tip: Keep the name as short as possible to avoid exceeding character limits when you build
on this application in the future.

2. Optional: If the application name is truncated, you can modify it by clicking it.

Concatenated application names that exceed 10 characters are truncated because they are
key parts to other rules, such as classes and rulesets.

3. Optional: In the Description field, enter more detailed information, such as the purpose of
the application.

4. From the Built on application list, select the name of an application. When you build on an
application, you can reuse and extend the functionality that it provides.
Options include:

 The base PegaRULES application

 The PegaDM application that supports decision-management features

 Framework applications

 Implementation applications

Tip: If you do not see a specific application in the list, review the Do not show this
application as a built-on choice in the New Application wizard check box on the
Application form.

5. Select an option from the Application Structure list to indicate how many class layers are
created in your new application.
Options include:

 Framework and Implementation — Adds two class layers to the built-on

application.

This option provides the most flexibility for future growth and reuse.

 Framework only — Adds one class layer to the built-on application.

You can reuse or extend a framework application later.

 Implementation only — Adds one class layer to the built-on application.

Implementation applications are typically not extended because they are

specialized.

6. In the Organization field, enter a unique name that starts with a letter and contains
alphanumeric characters or spaces.
 By default, the wizard sets the value in this field to the organization that is defined on your
Operator ID form.

7. Optional: Click the truncated organization name to modify it.

Concatenated organization names that exceed 4 characters are truncated because they are
key parts to other rules, such as classes and rulesets.

8. Optional: Click Configure advanced settings to access more options.

Defining business objectives in the New Application wizard

On the Business objectives form of the New Application wizard, you can define high-level goals, or
business objectives, for your new application. You work with this form when you create an enterprise
application.

To define business objectives:

1. Click Add business objective to add a row to the list of business objectives that are in your
built-on application.

2. In the text field that is displayed, enter a description of the business objective that is
measurable and outcome-focused.

3. Optional: Click the delete icon to remove a business objective that does not align with the
purpose of your new application.

After your application is created, you can reference your business objectives from specifications.

Adding case types in the New Application wizard

Case types are basically module names

Case types represent units of work you expect to accomplish in your application. Cases traditionally
have a lifecycle, and through a set of actions, accomplish a meaningful business outcome. It is easy to
add case types while building your application, so just capture enough to get started.

On the Case types form of the New Application wizard, you can add case types or import existing case
types to your new application, based on your built-on application. You work with this form when you
create an enterprise application.
Tip: Use extension points to enhance the functionality in this step of the wizard. For example, you
can automatically add rules and data from built-on applications to each of your newly created or
imported case types.
To add new case types:

Follow these steps when you are extending the PegaRULES or PegaDM application.

1. Click Add case type.

2. In the Name column, enter a case-type name that does not exceed 40 characters.

Case-type names must start with a letter and can contain alphanumeric characters,
ampersands, underscores, or hyphens.

3. Optional: In the Description column, enter more detailed information, such as the
purpose of the case type.

For each case type that you define, a case type named pyDefault is created with a set of standard,
supporting rules.
To import existing case types:

Follow these steps when you are extending a framework application.

Adding data types in the New Application wizard

What is data Type? Data Types are predefined tables in application.

Data types represent information that is necessary for a case to accomplish its actions or achieve its
business outcome. This data is often shared across multiple cases and possibly applications, and could
be stored local to this application or in an external system. It is easy to add data types while building
your application, so just capture enough to get started

On the Data types form of the New Application wizard, you can add data types or import existing data
types to your new application, based on your built-on application. You work with this form when you
create an enterprise application.
To add new data types:

Follow these steps when you are extending the PegaRULES or PegaDM application.

1. Click Add data type.

2. In the Name column, enter a data-type name that does not exceed 40 characters.

Data-type names must start with a letter and can contain letters, numbers, and hyphens.

3. Optional: In the Description column, enter more detailed information, such as the
purpose of the data type.

4. Select an option from the Reuse Layer list to indicate where the class for the data type is
created.
To import existing data types:
 Follow these steps when you are extending a framework application.

1. Review the list of data types in the framework application that will be added to your new
application.

By default, the check box next to each data type is selected.

2. Click an application name in the Additional Built-On Applications section to review a list
of data types that will be inherited.

3. Repeat step 2 for each list of data types that you want to inspect.

4. Optional: Clear the check box next to a data type to exclude it from the import process.

For each data type that you select, an existing data class is referenced by your new application.

After your application is created, you can use the Data Explorer to add more data types.

Template is Admin@OrganizationName
Green leaves are known as classes in pega.

Parent Class is HDFC-HDFCBank-Work. >>>>>>>> Loans , Paytm & Sample are subclasses.

HDFC-HDFCBank-Work: work pool

Subclasses are same as case name : Loans , Paytm & Sample

Refer below pic.

What is difference between case and class?

 Case is a module where we define our lifecycle of module. Like Adding Flows
 Class: Actual design is carried out here.
Example: for loan case actual design will be carried in Loan class.
Adding properties, Integration and rest other designs are done here.

Rules are mapped in flows> Flows are mapped in case option

A case is work which gives us a business outcome.The outcome of the case is the business
solution provided to the customer.

A class structure is used to organize the rules well mannered which helps for easy maintenance
and helps us for easily reuse of rules.

Case is a business process consists of a series of tasks that need to be completed and it establish
the logical progression of steps using manually, automatically and procedurally. Where as
Classes are created in the system, with names based on the Case names.
Any class which contains process flow pystartcase then it is a case.Every case type can be class,
but every class must not be a case.

Any application will have 3 WORK GROUPS:

1. Work Class group – Like HDFC-HDFCBank-Work <- This is a work glass group

Work Class group contains work classes.

Example of work class:

HDFC-HDFCBank-Work-Loans
HDFC-HDFCBank-Work-Paytm
HDFC-HDFCBank-Work-Sample

Note : Actual design is done here in Work Class Group.

2. Data Class group : HDFC-HDFCBank-Data

Contains Data Classes/Tables/Data Types.

We need to add this manually in application.

3. Integration class group : HDFC-HDFCBank-Int

Contains integration classes.

This is used when connecting to external services.(Connectors)
Class inheritance
Class inheritance is the method by which a child class can use all of the rules defined for a parent
class. The Pega 7 Platform supports two types of class inheritance: directed inheritance and pattern
inheritance.

Both types of class inheritance allow rules of ancestor classes to be inherited. However, class
inheritance does not apply to external classes, even if the class name contains a hyphen.

Directed inheritance

If we manually give inheritance it is direct inheritance.

Directed inheritance is the method by which a class inherits characteristics directly from a specified
parent class, regardless of any defined pattern inheritance

Pattern inheritance

Also known as pattern inheritance. This is generated by server.

Pattern inheritance is an optional method where a class inherits characteristics from other classes and
affects the first steps in the rule resolution algorithm. The name of the parent class is based on an
initial portion or substring of the name of the class. Pattern inheritance is set in the Rule-Obj-Class
rule.
Rule Type – Rule Type is a Component.

Right click on a class and then click on create. The list that appears is rule type.
q. What is rule?
Rule is template under rule types.
Example : when you click on decision then rule appears.

q. What is ruleset?
Container to store rules/records in application.
Ruleset are created automatically in background.

Suppose if AppName is HDFCBank & Org : HDFC

Now rulesets are : Work class: HDFCBank

Data Class: HDFC
Int Class : HDFCBankInt
How to create Data Table?

Click on Data> click on down arrow button>Add data type.

Now here you can enter the properties along with their format :
What is primary key?

The unique data that belongs to just one is called primary key.
Example: while creating Db of voters ; phone number and voter card number can be primary
keys

It is compulsory for atleast one field to be primary key.

Or in above case (refer screenshot) the SSIND is primary because its exclusive to each
person.

To make a record primary key:

>Click on sources>Click on “create a local sources”.

Choose your primary key:

Now click on next.

This will appear as primary key here.

How to add data class to application?
Data Class Format is : OrgName-Data-TableName
Property

Property is like a variable in Java.

There are 3 ways to create property.

1. Create a property.
2. Quick create a property.
3. Property Wizard.

Pega provides several tools that help manage properties

->The Data Explorer :
->Use the Data Explorer to add or remove data types.
->Always check if a suitable data type is available before creating a new one. ->Note
->Pega comes with many standard classes you can use directly in your application. Select an
existing data type and specify the data type you want to use.
->You can extend an existing data type if it only partly meets your needs.
->The Data Model Tab :
->You can use the Data model tab in the Case Designer to add or remove properties from
your case type. ->Note
->Properties are called fields in the Data model tab. ->Note
->Select Show reusable fields to display all fields inherited and available in the case type.
->When creating a new field, you need to specify a type.
->The options in the list pair the field with a control in the user interface. ->Note
->Type options are divided into three categories:
->simple : simple types are similar to the property types defined on the property itself.
->fancy : allow you to provide the capability to upload an attachment, show a location on a
map, or reference a user on the system.
->complex : to define page and page list properties. A field group is a page and a field group
(list) is a page list.
->Property Rule Form : ->Note ->Remembee
->contains the property definition.
->Because a property definition is a rule, it shares the benefits of versioning, inheritance, and
access control that the Pega 7 Platform provides to all rules.
->The property type cannot be changed after the property has been saved. ->Note
->Data Access section :
->to configure automatic data access and persistence settings.
->Use Manual if you are explicitly setting the value (for example, in a user interface). Other
options depends on the property type selected and are not covered in this lesson.
->Display and validation section :
->allows you to define how the property should appear on the screen by specifying a UI
control.
->You also have the option to specify a table with valid values for the property.

->Pega comes with a set of standard property rules.

->The standard properties have names that start with px, py, or pz. ->Note
->You cannot create new properties starting with px, py, or pz. ->Note
->px : Identifies special properties — your application can read but not write to these
properties.
->py : You can use these properties in your application.
->pz : Supports internal system processing — the meaning of values may change with new
product releases. Your application can read but not write to these properties.

A. Create a property
Here default property type is TEXT
TYPES OF
PROPERTIES

Single Value Page Advanced

Date Single Page Java Object

DateTime Page Group Java Object Group

Decimal Page List Java Object List

Double Java Property

Identifier Java Property List

Integer Value Group

Password Value List

Text

TextEncrypted

TimeOfDay
ADVANCED PROPERTY OPTIONS:

CLICK SAVE AND DONE.

B . QUICK CREATE A PROPERTY

CLICK ON Remove additional configuration options : This is difference between quick create and general create.
Click on orange tab : create and close
 C. PROPERTY WIZARD

CLICK ON CREATE PROPERTY

This screen will show last property.

Simply add field here and enter the data required.

Finally click on : “ Add to data explorer”

Records are of two types:

1. Static Records: Fixed records like Gender and DOB

2. Xx

Note : Here like if we select “ Gender” ; its ideal to choose TYPE as “PICKLIST” . Configure that type with “ MALE” &
“Female” option.
Note : You cannot use quick create property for static records.
For static records use only : 1. Create a property
2 Property wizard

Q. How to create a section?

Section contains Layouts & Controls . Layouts are combination of row and columns which is configured
according to client’s requirement.
 Types of layouts :

Dynamic layout.: Default.

Freeform layout
Repeating layout
Column layout
Tabbed layout.

About sections
Use sections in conjunction with harnesses to define the appearance of user forms, rule forms, or
composite portals.

A section defines the appearance and contents of one portion of a form.

Work information and functionality are grouped into sections by context and purpose. Each section
can be included in other sections so that you can reuse them in a variety of contexts.

The Pega 7 Platform contains dozens of standard harnesses and sections. You can copy and tailor
these standard forms to meet your application needs.
Layouts
Layouts organize properties and controls within a section.

Layout cells contain properties, labels, controls, or other sections. There are various types of layouts
that dictate how cells are arrayed. Layouts can be automatically converted into a sections so that
they can be reused in other harnesses, sections, or flow actions.

Controls
Information about a work item is entered or displayed in controls such as text areas, drop-down lists,
check boxes, or calendars. Many controls are configured so that they meet, without further
refinement, most of your process requirements. To add a control, drag and drop it onto a layout cell.

From the toolbar in a section, you can add layouts and controls to your section.

Layout

Dynamic Smart layout Freeform layout

Repeating
layout
layout

Basic

Advan
ced

Where referenced
Rules of the following types can reference a section:

 Harnesses

 Other sections
 Paragraph rules, as the contents of a pop-up SmartInfo window.

q. How to use properties in default layout?

Go to sections

Now drag and drop the properties to sections.

How to edit control:

Click on the sky blue light highlighted icon .. Like here you see in country property at end .
Click on that . You will get below option.

Here click on Change now:

You will get these options:
How to change Layout?

Click on default option tab..

On clicking a gear button will appear.

Click on gear button

You can now choose the layout.

You can also add a new layout

Click on layout and choose a layout. Drag that layout wherever you want to add in previous layout.
This is how tis gets added:

We can also add layout inside layout. This will appear s Layout 1.1

Something like this:

MAPPING A SECTION IN FLOWACTION

Flowaction : container of section.

We add validation and business logic here.
 ADDING FLOW:

Flow rule is the fundamental representation of a business process in process commander.

1. Explain about types of Flows?

A flow rule that contains no assignments, and so can execute from start to end without

human input, is known as a straight-through process.

A flow rule that consists only of assignments or decisions and meets other criteria is

known as a screen flow.

A flow that creates a new work object is called a starter flow.

A flow that is called by another flow is known as a subflow, the calling flow is called

parent flow.

2. What is a screen flow, why it is used?

 A series of forms that each require only one or few questions to be answered. After submitting a
form, user receives with another simple forms with more fields that my depend on previous answers.
At any point user can go to previous forms to review or change previous answers.

To make a screen flow, create a new flow rule and select screen flow in the Template field.

3. Can we start an application with a screen flow? If yes, how? If no, why?

A screen flow rule can’t be a starter flow rule. Use the regular flow to create WorkObject.

Call the screen flow as sub flow

we can’t start an application with a screen flow because “Create New Object” option is disabled
under process tab.

A screen flow can operate on a temporary work object, this is never saved to Data Base.

In screen flow Flowactions are referenced by assignment shape rather than connectors.

4. How can we call one flow from another flow?

By using subflow shape. Just drag a subflow shape and fill in appropriate values ,depending upon
what we choose among “On Current Work item”, “On Another Work Item” or “On Embedded Page”.

5. When do we say that a work object is resolved? Can a work object be resolved manually?

When the flow reached the end shape, the work object gets resolved.

Manually it can be resolved through UpdateStatus activity and provide the values for “StatusWork”
parameter as Resolved.

6. How to restrict a flow to particular users?

By using privileges and when conditions under process tab of the flow instance.

7. Flows use three types of status:

 Work object status reflects the current state of a work object based on its position in the flow.

 Assignment status records the user’s judgment about an assignment on the worklist.

 Activity status reflects the outcome of a Utility or Flow shape.

This Is what you get as default when you create a flow.

Flow Shapes
The available shapes are

1) Start task 2)Assignment 3)Assignment

service 4)Comment 5)Connector 6)Decision

7) Subflow 8)Flow
end 9)Fork 10)Integrator 11)Notification 12)Router 13)Spin-off

14)Split-join 15)Split-for each 16)Pool with swin lanes 17)Ticket 18)Utility

1. Explain about Assignment shape?

An assignment is an instance of a class derived from the Assign- class.

Assignments record a temporary condition of an open work object within an executing flow.
 For every Assignment , add at least one flow action .

The assignment normally appears on the work list of the user who executes the flow.

2. Explain about Connectors?

To connect a shape element in the flow with the next shape element. To indicate a possible path for
the flow execution.

3. Explain about Notify shape?

A Notify can send an e-mail message to a work party.Connect the notify shape to the bottom edge of
an assignment shape.

4. Explain about Router shape?

Sends an assignment to a user, workbasket, or agent other than the current user.

Associate a Router task with an assignment task. This activity determines which worklist or
workbasket is to contain the assignment.

5. Explain about Spin-Off shape?

When a work object advancing through a flow reaches the Spin-Off shape, process commander
starts execution of a different flow, using the current work object or different work object.

Processing in the current flow rule continues in parallel, without waiting for the other flow to
complete.

Use the Spin-Off shape to start a Synchronous flow execution.

6. Explain about Split-Join shape?

Split-Join shape is used to multiple subflows of our flow be completed before the current flow
continues execution.

This allows subflows to execute asynchronously, in parallel.

The Split-Join shape must contain at least two called flows.

7. Explain about Split-ForEach shape?

Split-ForEach shape is used to iterate over the pages of a Page List or Page Group property. For
each page, we can conditionally start a flow execution for the work object.

Processing in the orginal flow pauses while sub flow execute.

We can’t use Split-foreach shape to create work objects.

The embedded page must exist before the Split-foreach shape is reached.

8. Explain about Fork shape?

The fork shape is used to choose one of a few different paths (connectors) based on tests on the
work object.

At runtime, the system evaluates the conditions on each outgoing connector, starting with the
connector assigned the highest likelihood. The flow execution continues along the first connector
that evaluates to True.

9. Explain about Decision shape?

Decision shape is used to reference a map value rule, decision table rule, decision tree rule or a
Boolean expression.

At runtime, the system evaluates the decision rule based on inputs from the flow and the work
object, and chooses one of the outgoing connectors based on the result.

10. Explain about Ticket shape?

We can start the execution point in the flow at any point in the flow by using Ticket shape.

The ticket is same as GOTO in programming language.

Ticket creation:

1. Create the Ticket

2. Drag a ticket shape to where we want to jump in the flow and Complete the Ticket Properties panel

3. To configure the ticket in activity, Call the SetTicket activity and pass Ticket name

4. Create separate flow action and mention above activity as post activity in flow action.

5. Mention this FLOWACTION as LOCAL ACTION in assignment from where we want to jump.

6. At the time of running the flow By default Connector Action is Displayed.

 At the time of run the flow we need to select the local action at that particular assignment where
we mention the ticket activity.

11. Explain about Utility shape?

This is used to call activity rule (logic) in Flow.

Each utility task references an activity with an Activity Type of Utility.

Utility activity is defined in a class derived from the Work- or Data- base class and activity of type
Utility.

12. Explain about Integrator shape?

This is used to call activity rule (logic) in Flow.

Integrator activity identifies an activity that connects our process commander system to an external
system to send or receive data.

For example integration task can connect to a customer data base to retrieve account balances or
verify account numbers and status.

Integrator task use activities that call connector rules.

Difference between Integrator and Utiliy shape:

Both are used to call activity rule (logic) in Flow. But integrator is only used when connector
method is used. For rest all normal method utility shape is used.

13. Explain about SubFlow shape?

Sub Flow shape may represent any of the following:

 A branch to another flow without returning (one or more incoming connectors, no outgoing
connectors)

 A call to another flow with return (one or more incoming connectors, one or more outgoing
connectors)

 Part of a Split/Join or Split-forEach shape (at least one incoming and one outgoing connector)

A flow rule that is branched to or called by another is sometimes informally called a subflow.
 In subflow we can define flow on current work item or another work item.

14. Explain with an example, the difference between a Decision shape and a Fork?

A decision task is a shape on a flow rule that references a rule of one of three types:

1)A map value rule (Rule-Obj-MapValue rule type) 2) A decision tree rule (Rule-Declare-
DecisionTree rule type)

3) A decision table rule (Rule-Declare-DecisionTable rule type)

At runtime, the system evaluates the decision rule to determine how a work object progresses
through the flow. The work object progresses along one of the connectors leading from this shape,
depending on the outcome of the decision rule.

On the other hand fork checks the conditions directly on the object and unlike decision shape it
never asks for a Decision tree, table or map value and two or more connectors can emanate from a
fork shape.

15. Consider this scenario: After a work object had reached a particular stage in a flow, I need to
run two flows in parallel to each other. How this can be achieved?

This can be achieved by using Spin-Off shape. Just drag the spin off smart shape and fill in the
appropriate values depending upon what you choose among “On Current Work item”, “On Another
Work Item” or “On Embedded Page”.

So the flow started by this shape will be called a subflow and the original flow as parent flow.

Subprocess Shape :

They are used to call one flow in another flow,

3 cases are here:

1. Screen flow into screen flow

2. Screen flow in process flow
3. Process flow in process flow

Note : you cannot call process flow in screen flow.

PRACTICAL

Aim: Fetch Single record.

Primary Key – StudentID

There are functions like Fetch Multiple also.

The steps will be as follows:

1. Create data tables . In real time we also import records but in personal edition But here we
will input it manually.
2. Add Properties (Work Class)
3. Section Rule ( 2 section)
4. Flowaction Rule (2 flowaction)
5. Activity Rule.
6. Flow Rule. (2 Flowaction and one activity)
7. Test and debug

In case of Fetch Single Action:

For Work Class you need to give : Any Page name.

However for Data Class there is a default page : Primary (Default page)