Skip to main content

PDN

MY ACCOUNT
CONTACT US
LOG OUT

Products

Academy

Support

Forums

Resources

1.

Implementation Methodology, DCO

2.

Basics

3.

Create applications with the New Application wizard

Create applications with the New

Application wizard
Suggest edit
Comments(16)

20

40

60

80

100
Total votes: 14

You can use the New Application wizard to build applications in a few minutes with a
minimum of technical expertise. The New Application wizard guides you through the
process of specifying basic configuration requirements for your application. You can use
advanced options to customize the settings to suit your specific design requirements. The
system generates the application and its structure to get you started in Designer Studio.
You build an application in four steps:
1.

Configure your application settings in Step 1: Application settings.

2.

Define the business objectives in Step 2: Business objectives.

3.

Add case types to your application in Step 3: Case types.

4.

Add data types to your application in Step 4: Data types.

This article provides a walkthrough of the process by using a basic scenario. In this
scenario, the PCO Loan Company acquired a Purchase Request application that it wants to
extend for use in a regional sales office. As the system administrator, you use the New
Application wizard to build the implementation application according to your organization's
requirements.

Starting the New Application wizard

To start the New Application wizard:

1.

Click Application menu > New Application in the Case Designer header.

2.

Click Create new application to start creating an application.

Step 1: Application Settings displays and contains default values.

Step 1: Application settings

Specify the following application settings:
1.

In the Application field, enter a unique name that starts with a letter and can contain
alphanumeric characters, ampersands, underscores, or hyphens. This name is
displayed in portals, menus, and forms.
For this example, enter: Cambridge Purchase Request.

2.

Tab out of the field. The name is displayed in the Description field.
In addition, the New Application wizard removes the spaces from the full name to
create a short name, which serves as a unique application identifier that the system

uses for processing and for naming the application's classes. Application names are
truncated because they are key parts to other rules, such as classes and rulesets. This
application short name appears under the Application field.

3.

4.

To change the short name, click the name to open the Application short
name modal dialog box.
Enter cambpur, and click OK.

If you intend to extend your application by using the New Application wizard, keep the name
as short as possible to avoid exceeding class name character limits. The class name limit is
56 characters. The limit for an application short name is 14 characters.

5.

Enter a high-level description of the application's purpose and its basic design
requirements.

After you create your application, you can view or update the description on the Application
Overview landing page in Designer Studio.
6.

Review the values in the following fields:

o

Built on application Specifies the application that you want to extend. By

default, the application is the one that you are currently working in, Purchase
Application. Keep this value.

Application structure Indicates how many class layers are created in your
application. Keep the default, Framework and Implementation. In addition to
the new Cambridge Purchase Request application that you are putting into
production, the New Application wizard creates an application that you can
extend for reuse elsewhere in the organization. For example, you might want to
extend the application for use in other regional offices.

Organization Specifies the organization that is associated with the

application. By default, this organization is the one defined in your operator ID.
This organization value is used to name the organization record, the

organization classes, and the organization ruleset. Keep the default, Pco.com.

Adding a division class layer to your application

A requirement for this application states that a layer of division classes must contain rule
and data records that can be reused by other applications. A division is the middle level of
the three-level organization hierarchy and is available for use in every application. Divisions
are below the organization level and above the organization unit level.
To create a division class layer in your new application:
1.

Click Configure advanced settings, which is located below the Organization field.
The Advanced configuration dialog box opens. Some of the settings that you defined
in "Step 1: Application settings" are also displayed in this dialog box. For example, the
short name is displayed in the Application record name and the Application

layer fields.

2.

Select the Generate reusable division records check box. This setting displays
the Division layer field in the Class structure - Implementation layer section.

By default, the New Application wizard truncates the Division name value to four
characters. The Division layer value is used in the division class names and ruleset.
3.

Click Save to apply your changes.

4.

Click Next at the bottom of Step 1 to proceed to "Step 2: Business objectives."

Step 2: Business objectives

Business objectives define the expected business outcomes for the new application. By
default, the New Application wizard reuses the values in the built-on application, Purchase
Application.
To add a business objective that is specific to the Cambridge Purchase Request application:
1.

Click Add business objective to add a row and enter an objective.

2.

Click Next to proceed to "Step 3: Case types."

After you create your application, you can update the objectives on the Application Overview
landing page.

Step 3: Case types

In this step, you import the case types in the built-on application or ones inherited from other
built-on applications (excluding PegaRULES).
1.

Select the case types to import. In this example, the list includes the top-level case
type Vendor Maintenance and all of its related subcase types.

2.

If you do not want to import a case type, clear its check box. However, for this
example, import all the case types.

3.

Click Next to proceed to "Step 4: Data objects."

The New Application wizard only imports subcase types that have the Include case types
in the Create menu check box selected on the Cases and Data tab of the built-on
application's rule form.

Step 4: Data objects

Use this step to select the data objects in the built-on application, or those inherited from
another built-on application, that you want to reuse. The New Application wizard does not
generate new data classes. The wizard creates links between the new application and the
selected data classes.

In this example, you want to use all the data objects, so do not clear any of the check boxes.

Previewing the application

To preview the class structure that the New Application wizard creates:
1.

Click Preview. The Application preview dialog box displays the names of the
organization, division, framework, and implementation class layers. The Other section

includes access group and access role name data items that are created for the new
application.

2.

Expand Cambridge Purchase Request Implementation Layer to display the

classes and the ruleset names.

3.

4.

To preview the case types in the application's work pool, expand Work (Default
Work Pool).

Click Close preview to exit the dialog box and return to step 4.

Creating the application and starting development

When you are satisfied with the class structure, you can create the application.
1.

Click Create at the bottom of Step 4.

When the New Application wizard finishes creating the application, the Designer Studio
Home page opens and displays the Application Overview landing page. You are now
ready to develop your new application.

2.

On the Application Overview landing page, develop your application profile in

the Details section. Then, use Case Explorer to configure your application's case types

and processes.

Related Content:

Managing your application profile from the Application Overview landing page

Express applications

Add new comment

Subscribe

Comments

October 16, 2013 - 2:12pm

Harikrishna Srivaram
Excellent case management and Data integration

reply

reply

October 25, 2013 - 12:11am

Ravi Kumar Pisupati
Nice article!

December 9, 2013 - 8:06am

Meena Murugesan
Great! How to handle integeration ( MQ, SOAP, Email & DB )?

reply

reply

January 23, 2014 - 1:35pm

Sanjeevan Naguleswaran
great article!

May 21, 2014 - 12:54pm

Debasish Sahoo
nicely written and understandable.....

reply

June 14, 2014 - 10:35am

Ednatej Pusuluri
When the application is created in "Admin" role,the application is not accessible in
"SystemArchitect" role.Why?Can anyone please explain?

reply

August 23, 2014 - 12:30am

Moota Vijay Kumar
Is there any wizard to discard these changes if at all want to revert the above application
creation and delete the rules, classes and rulesets.

reply

reply

September 17, 2014 - 11:40am

NEPAL KOIRI
Nice Article.It is very useful.

October 13, 2014 - 1:26pm

Veera Reddy Kesari
Nice Article.It is very useful.

reply

reply

February 24, 2015 - 3:50pm

shaikshah vali
Nice Understanding Way

Add new comment

Your name

sivan740
Comment *
Source

FormatStyles

Switch to plain text editor

POST
Node ID: 40756
Published: October 7, 2013
Updated: March 16, 2016
Product Version: Pega 7.1.x
Topic: Designer Studio

Index
Implementation Methodology, DCO
Application Sizing Wizard worksheet template now includes business impact
Enabling historical compliance score data
New Business impact optimization dashboard
Basics
Implementation and Methodology Overview
Tutorial: Merging branches
Tutorial: Using branches for parallel development
Ten Guardrails to Success
Delivery Keys to Success

Delivery@Pega
Developer best practices in Pega 7
About application specifications and requirements
Create applications with the New Application wizard
Express applications
Guided development through guardrails
How to model the user interface of your application before all properties are defined (PRPC
5.5)
How to model the user interface of your application before all properties are defined (PRPC
6.1)
Naming standards for Case Lifecycle Management components, and for records, classes,
tables, and other objects
PRPC 6.3 Dictionary of Rule Warnings
Using the Application Express to Prototype Applications
What is a Servicing Backbone?
When and how to use the private check-out feature
Associating project specifications with business impact and complexity
Compliance score trend reporting
Using Branch RuleSets and Merging for Parallel Development
Direct Capture of Objectives (DCO)
About the Application Overview landing page
Understanding the Class structure and RuleSets generated by the Application Accelerator
How to manage specifications and requirements from the Application Profile landing page
How to use the DCO Compatibility tool
Managing your application profile from the Application Overview landing page
DCO 6.2 and 6.3
Adding a Work Type to a Framework and to its Implementation Layer

DCO 6.2 and 6.3 - Creating Application Profiles and Discovery Maps
DCO 6.2 and 6.3 - Using the Application Accelerator
DCO 6.2 and 6.3 - Using the Application Document Wizard
DCO 6.2 and 6.3 - Working with Application Use Cases and Requirements
Introducing PRPC 6.2 - Implementation and Methodology
DCO 6.1
DCO 6.1 - About the Direct Capture of Objectives
DCO 6.1 - Upgrading from older versions of DCO
DCO 6.1 - Creating Discovery Maps
DCO 6.1 - Creating an Application Profile
DCO 6.1 - Extending the Document wizard
DCO 6.1 - How to customize Application Document templates
DCO 6.1 - Sharing and Merging Application Profiles
DCO 6.1 - Using the Application Accelerator
DCO 6.1 - Using the Application Document Wizard
DCO 6.1 - Using the DCO Application Enablement Wizard
DCO 6.1 - What's New
DCO 6.1 - Working with Application Requirements
DCO 6.1 - Working with Application Use Cases
Troubleshooting: Hotfixes for 6.1 SP2 Direct Capture of Objectives are available for selfservice
DCO 3.2
About the Direct Capture of Objectives (DCO)
DCO 3.2 - Creating an application profile
DCO 3.2 - Enabling DCO access
DCO 3.2 - Extending Document Wizard templates

DCO 3.2 - Using the DCO Enable Application Wizard

DCO 3.2 - Using the Enterprise Application Accelerator
DCO 3.2 - What's New
DCO 3.2/3.1 - Using the Application Document Wizard
DCO 3.2/3.1 - Working with Application Requirements
DCO 3.2/3.1 - Working with Application Use Cases
DCO 3.1
DCO - Release Notes
DCO 3.1 - Creating an Application Profile
DCO 3.1 - Enabling DCO Access
DCO 3.1 - Using the Enterprise Application Accelerator
Enhancements to the Direct Capture of Objectives
How to add Entity Relationship diagrams and screenshots to an Application Document
How to add application details in the Application Document Wizard
How to build a screenshot catalog in the Application Document Wizard
How to conduct "Prep and Review" style DCO sessions
How to order content in the Application Document Wizard
How to prevent IE warning 'Stop Running This Script?' when adding Application requirements
Updating customized Application Document templates with server-side document generation
Using the Application Document Wizard
Business Analyst Resources
Business Analyst Resources Overview
Using Pega BPM with PRPC
Using Pega Scrum with PRPC

US: +1 (617) 374 9600

UK: +44(0) 118 9591150

Australia: +61 2 9581 7000

CONTACT US

PRIVACY & SECURITY

TERMS OF USE

US - EU SAFE HARBOR

TRADEMARKS

2016 Pegasystems Inc.