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)