creating application.docx

8/15/2019 creating application.docx

1/26

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)

https://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#main-contenthttps://pdn.pega.com/https://pdn.pega.com/userhttps://pdn.pega.com/contact-ushttps://pdn.pega.com/user/logouthttps://pdn.pega.com/pega-products-applicationshttps://pdn.pega.com/about-pega-academyhttps://pdn.pega.com/search/product-support/%20?f%5B0%5D=im_field_article_type%3A166&f%5B1%5D=im_field_article_type%3A165https://pdn.pega.com/forumhttps://pdn.pega.com/about-pega-discovery-networkhttps://pdn.pega.com/implementation-methodology-dcohttps://pdn.pega.com/basics-5https://pdn.pega.com/suggest-edit-article?id=40756&[email protected]&alias=create-new-applications-quickly-and-easily-new-application-wizardhttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#commentshttps://pdn.pega.com/https://pdn.pega.com/userhttps://pdn.pega.com/contact-ushttps://pdn.pega.com/user/logouthttps://pdn.pega.com/pega-products-applicationshttps://pdn.pega.com/about-pega-academyhttps://pdn.pega.com/search/product-support/%20?f%5B0%5D=im_field_article_type%3A166&f%5B1%5D=im_field_article_type%3A165https://pdn.pega.com/forumhttps://pdn.pega.com/about-pega-discovery-networkhttps://pdn.pega.com/implementation-methodology-dcohttps://pdn.pega.com/basics-5https://pdn.pega.com/suggest-edit-article?id=40756&[email protected]&alias=create-new-applications-quickly-and-easily-new-application-wizardhttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#commentshttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#main-content


2/26

• 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 wizardTo start the New Application wizard:

https://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard?rate=DBlrGaUstT5QOp6mrCN1-Gq1K9rDThRJ7AK5B5DvKVUhttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard?rate=55ylIT9Ilxl0-LTezB23Qa09fcGn5p1Nj_iuP_s9fHYhttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard?rate=hrpDmiX2iByS_BYjUtf_NWHOd-CwrBR5luqgGCP3xNAhttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard?rate=2yzO3fVC-_Gj1W02ZRJjLKXcd6jnKGB3x0NaRwfX5eIhttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard?rate=RYS91QXCrDbdaBTeGF9fHajJPIzWuAD5DM-6fo8It-Ehttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#Step%201https://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#Step%202https://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#Step%203https://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#Step%204https://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard?rate=DBlrGaUstT5QOp6mrCN1-Gq1K9rDThRJ7AK5B5DvKVUhttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard?rate=55ylIT9Ilxl0-LTezB23Qa09fcGn5p1Nj_iuP_s9fHYhttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard?rate=hrpDmiX2iByS_BYjUtf_NWHOd-CwrBR5luqgGCP3xNAhttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard?rate=2yzO3fVC-_Gj1W02ZRJjLKXcd6jnKGB3x0NaRwfX5eIhttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard?rate=RYS91QXCrDbdaBTeGF9fHajJPIzWuAD5DM-6fo8It-Ehttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#Step%201https://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#Step%202https://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#Step%203https://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#Step%204


3/26

1. ClickApplication menu > Ne Application in the Case Designer header.

2. ClickCreate ne application to start creating an application.


4/26

Step !" Application Settin#s displays and contains default values.

Step 1: Application settingsSpecify the following application settings:

1. In theApplication field, enter a unique name that starts with a letter and can contain

alphanumeric characters, ampersands, underscores, or hyphens. This name isdisplayed in portals, menus, and forms.

For this example, enter:Cambridge Purchase Request.

2. Tab out of the field. The name is displayed in the$escription 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


5/26

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 theApplicationfield.

3. To change the short name, click the name to open theApplication s%ort

name modal dialog box.

4. Entercambpur, and clickO&.

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.


6/26

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 'uilt 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.

o Application structure – Indicates how many class layers are created in yourapplication. Keep the default,Framework and mplementation. 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.

o Or#ani(ation – 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


7/26

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

Adding a di"ision class la#er to #our 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. ClickCon)i#ure ad*anced settin#s, whichis located below theOr#ani(ation field.

TheAd*anced con)i#uration 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 theApplication record nameand theApplication


8/26

layerfields.


9/26

2. Select theGenerate reusa+le di*ision records check box. This setting displays

the$i*ision layer field in theClass structure , -mplementation layer section.

By default, the New Application wizard truncates the$i*ision name value to four

characters. The$i*ision layer value is used in the division class names and ruleset.

3. ClickSa*e to apply your changes.

4. ClickNe.tat the bottom of Step 1 to proceed to "Step 2: Business objectives."

Step $: %usiness ob&ecti"esBusiness 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. ClickAdd +usiness o+/ecti*e to add a row and enter an objective.


10/26

2. ClickNe.tto proceed to "Step 3: Case types."

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

landing page.

Step ': Case t#pesIn 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 casetype(endor )aintenance 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. ClickNe.tto proceed to "Step 4: Data objects."

The New Application wizard only imports subcase types that have the-nclude case types

in t%e Create menu check box selected on theCases and $atatab of the built-on

application's rule form.


11/26

Step *: +ata ob&ectsUse 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.


12/26

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

Pre"iewing the application

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

1. ClickPre*ie. TheApplication pre*ie dialog box displays the names of the

organization, division, framework, and implementation class layers. TheOt%er section


13/26

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

application.


14/26

2. ExpandCam+rid#e Purc%ase Re0uest -mplementation Layer to display the

classes and the ruleset names.


15/26

3. To preview the case types in the application's work pool, expand1or2 3$e)ault

1or2 Pool4.

4. ClickClose pre*ie to exit the dialog box and return to step 4.

Creating the application and starting de"elopment

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

1. ClickCreateat 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$etails section. Then, use Case Explorer to configure your application's case types


16/26

and processes.

Related Content:

• Managing your application profile from the Application Overview landing page

• Express applications

• Add new comment

•

Subscribe

Comments

https://pdn.pega.com/node/44826https://pdn.pega.com/node/325636https://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#comment-formhttps://pdn.pega.com/flag/flag/subscribe_node/40756?destination=node/40756&token=6tLL8Kih1C6c3khGp3P444CdMTOP2Raq99wId0KqP_0https://pdn.pega.com/node/44826https://pdn.pega.com/node/325636https://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizard#comment-formhttps://pdn.pega.com/flag/flag/subscribe_node/40756?destination=node/40756&token=6tLL8Kih1C6c3khGp3P444CdMTOP2Raq99wId0KqP_0


17/26

October 16, 2013 - 2:12pm

Harikrishna Srivaram

Excellent case management and Data integration

• reply

October 25, 2013 - 12:11am

Ravi Kumar Pisupati

Nice article!

• reply

https://pdn.pega.com/user/20996https://pdn.pega.com/comment/reply/40756/76338https://pdn.pega.com/user/71421https://pdn.pega.com/comment/reply/40756/76381https://pdn.pega.com/user/20996https://pdn.pega.com/comment/reply/40756/76338https://pdn.pega.com/user/71421https://pdn.pega.com/comment/reply/40756/76381


18/26

December 9, 2013 - 8:06am

Meena Murugesan

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

• reply

January 23, 2014 - 1:35pm

Sanjeevan Naguleswaran

great article!

• reply



19/26

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



20/26

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

September 17, 2014 - 11:40am

NEPAL KOIRI

Nice Article.It is very useful.

• reply



21/26

October 13, 2014 - 1:26pm

Veera Reddy Kesari

Nice Article.It is very useful.

• reply

February 24, 2015 - 3:50pm

shaikshah vali

Nice Understanding Way

• reply

Add new commentYour name



22/26

sivan740

Comment *

Source Format Styles

◢

Switch to plain text editor

POSTNode ID: *,-./Published: 0ctober - $,1'Updated: )arch 1/ $,1/Product Version: Pega -!1!2Topic: +esigner Studio

nde2Implementation 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

http://void%28%27source%27%29/http://void%28%27source%27%29/http://void%28%27paragraph%20format%27%29/http://void%28%27paragraph%20format%27%29/http://void%28%27formatting%20styles%27%29/https://pdn.pega.com/implementation-methodology-dcohttps://pdn.pega.com/release-note/application-sizing-wizard-worksheet-template-now-includes-business-impacthttps://pdn.pega.com/release-note/enabling-historical-compliance-score-datahttps://pdn.pega.com/release-note/new-business-impact-optimization-dashboardhttps://pdn.pega.com/implementation-and-methodology-overviewhttps://pdn.pega.com/tutorial-merging-brancheshttps://pdn.pega.com/tutorial-using-branches-parallel-developmenthttps://pdn.pega.com/ten-guardrails-successhttps://pdn.pega.com/delivery-keys-successhttp://void%28%27source%27%29/http://void%28%27cut%27%29/http://void%28%27copy%27%29/http://void%28%27paste%27%29/http://void%28%27paste%20as%20plain%20text%27%29/http://void%28%27paste%20from%20word%27%29/http://void%28%27%27%29/http://void%28%27undo%27%29/http://void%28%27redo%27%29/http://void%28%27find%27%29/http://void%28%27replace%27%29/http://void%28%27select%20all%27%29/http://void%28%27remove%20format%27%29/http://void%28%27image%27%29/http://void%28%27table%27%29/http://void%28%27insert%20special%20character%27%29/http://void%28%27create%20div%20container%27%29/http://void%28%27show%20blocks%27%29/http://void%28%27insert%20code%20snippet%27%29/http://void%28%27paragraph%20format%27%29/http://void%28%27formatting%20styles%27%29/http://void%28%27bold%27%29/http://void%28%27italic%27%29/http://void%28%27underline%27%29/http://void%28%27strike%20through%27%29/http://void%28%27subscript%27%29/http://void%28%27superscript%27%29/http://void%28%27insert/Remove%20Numbered%20List')http://void%28%27insert/Remove%20Bulleted%20List')http://void%28%27decrease%20indent%27%29/http://void%28%27increase%20indent%27%29/http://void%28%27block%20quote%27%29/http://void%28%27align%20left%27%29/http://void%28%27center%27%29/http://void%28%27align%20right%27%29/http://void%28%27justify%27%29/http://void%28%27text%20direction%20from%20right%20to%20left%27%29/http://void%28%27text%20direction%20from%20left%20to%20right%27%29/http://void%28%27link%27%29/http://void%28%27unlink%27%29/http://void%28%27anchor%27%29/https://pdn.pega.com/implementation-methodology-dcohttps://pdn.pega.com/release-note/application-sizing-wizard-worksheet-template-now-includes-business-impacthttps://pdn.pega.com/release-note/enabling-historical-compliance-score-datahttps://pdn.pega.com/release-note/new-business-impact-optimization-dashboardhttps://pdn.pega.com/implementation-and-methodology-overviewhttps://pdn.pega.com/tutorial-merging-brancheshttps://pdn.pega.com/tutorial-using-branches-parallel-developmenthttps://pdn.pega.com/ten-guardrails-successhttps://pdn.pega.com/delivery-keys-success


23/26

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

https://pdn.pega.com/deliverypegahttps://pdn.pega.com/developer-best-practices-pega-7https://pdn.pega.com/about-application-specifications-and-requirementshttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizardhttps://pdn.pega.com/express-applicationshttps://pdn.pega.com/guided-development-through-guardrailshttps://pdn.pega.com/how-model-user-interface-your-application-all-properties-are-defined-prpc-55https://pdn.pega.com/how-model-user-interface-your-application-all-properties-are-defined-prpc-55https://pdn.pega.com/how-model-user-interface-your-application-all-properties-are-defined-prpc-61https://pdn.pega.com/how-model-user-interface-your-application-all-properties-are-defined-prpc-61https://pdn.pega.com/naming-standards-case-lifecycle-management-components-and-records-classes-tables-and-other-objectshttps://pdn.pega.com/naming-standards-case-lifecycle-management-components-and-records-classes-tables-and-other-objectshttps://pdn.pega.com/prpc-63-dictionary-rule-warningshttps://pdn.pega.com/using-application-express-prototype-applicationshttps://pdn.pega.com/what-servicing-backbonehttps://pdn.pega.com/when-and-how-use-private-check-out-featurehttps://pdn.pega.com/associating-project-specifications-business-impact-and-complexityhttps://pdn.pega.com/compliance-score-trend-reportinghttps://pdn.pega.com/using-branch-rulesets-and-merging-parallel-developmenthttps://pdn.pega.com/about-application-overview-landing-pagehttps://pdn.pega.com/understanding-class-structure-and-rulesets-generated-application-acceleratorhttps://pdn.pega.com/how-manage-specifications-and-requirements-application-profile-landing-pagehttps://pdn.pega.com/how-use-dco-compatibility-toolhttps://pdn.pega.com/managing-your-application-profile-application-overview-landing-pagehttps://pdn.pega.com/adding-work-type-framework-and-its-implementation-layerhttps://pdn.pega.com/deliverypegahttps://pdn.pega.com/developer-best-practices-pega-7https://pdn.pega.com/about-application-specifications-and-requirementshttps://pdn.pega.com/create-new-applications-quickly-and-easily-new-application-wizardhttps://pdn.pega.com/express-applicationshttps://pdn.pega.com/guided-development-through-guardrailshttps://pdn.pega.com/how-model-user-interface-your-application-all-properties-are-defined-prpc-55https://pdn.pega.com/how-model-user-interface-your-application-all-properties-are-defined-prpc-55https://pdn.pega.com/how-model-user-interface-your-application-all-properties-are-defined-prpc-61https://pdn.pega.com/how-model-user-interface-your-application-all-properties-are-defined-prpc-61https://pdn.pega.com/naming-standards-case-lifecycle-management-components-and-records-classes-tables-and-other-objectshttps://pdn.pega.com/naming-standards-case-lifecycle-management-components-and-records-classes-tables-and-other-objectshttps://pdn.pega.com/prpc-63-dictionary-rule-warningshttps://pdn.pega.com/using-application-express-prototype-applicationshttps://pdn.pega.com/what-servicing-backbonehttps://pdn.pega.com/when-and-how-use-private-check-out-featurehttps://pdn.pega.com/associating-project-specifications-business-impact-and-complexityhttps://pdn.pega.com/compliance-score-trend-reportinghttps://pdn.pega.com/using-branch-rulesets-and-merging-parallel-developmenthttps://pdn.pega.com/about-application-overview-landing-pagehttps://pdn.pega.com/understanding-class-structure-and-rulesets-generated-application-acceleratorhttps://pdn.pega.com/how-manage-specifications-and-requirements-application-profile-landing-pagehttps://pdn.pega.com/how-use-dco-compatibility-toolhttps://pdn.pega.com/managing-your-application-profile-application-overview-landing-pagehttps://pdn.pega.com/adding-work-type-framework-and-its-implementation-layer


24/26

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 self-

service

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

https://pdn.pega.com/dco-62-and-63-creating-application-profiles-and-discovery-mapshttps://pdn.pega.com/dco-62-and-63-using-application-acceleratorhttps://pdn.pega.com/dco-62-and-63-using-application-document-wizardhttps://pdn.pega.com/dco-62-and-63-working-application-use-cases-and-requirementshttps://pdn.pega.com/introducing-prpc-62-implementation-and-methodologyhttps://pdn.pega.com/dco-61-about-direct-capture-objectiveshttps://pdn.pega.com/dco-61-upgrading-older-versions-dcohttps://pdn.pega.com/dco-61-creating-discovery-mapshttps://pdn.pega.com/dco-61-creating-application-profilehttps://pdn.pega.com/dco-61-extending-document-wizardhttps://pdn.pega.com/dco-61-how-customize-application-document-templateshttps://pdn.pega.com/dco-61-sharing-and-merging-application-profileshttps://pdn.pega.com/dco-61-using-application-acceleratorhttps://pdn.pega.com/dco-61-using-application-document-wizardhttps://pdn.pega.com/dco-61-using-dco-application-enablement-wizardhttps://pdn.pega.com/dco-61-whats-newhttps://pdn.pega.com/dco-61-working-application-requirementshttps://pdn.pega.com/dco-61-working-application-use-caseshttps://pdn.pega.com/troubleshooting-hotfixes-61-sp2-direct-capture-objectives-are-available-self-servicehttps://pdn.pega.com/troubleshooting-hotfixes-61-sp2-direct-capture-objectives-are-available-self-servicehttps://pdn.pega.com/about-direct-capture-objectives-dcohttps://pdn.pega.com/dco-32-creating-application-profilehttps://pdn.pega.com/dco-32-enabling-dco-accesshttps://pdn.pega.com/dco-32-extending-document-wizard-templateshttps://pdn.pega.com/dco-62-and-63-creating-application-profiles-and-discovery-mapshttps://pdn.pega.com/dco-62-and-63-using-application-acceleratorhttps://pdn.pega.com/dco-62-and-63-using-application-document-wizardhttps://pdn.pega.com/dco-62-and-63-working-application-use-cases-and-requirementshttps://pdn.pega.com/introducing-prpc-62-implementation-and-methodologyhttps://pdn.pega.com/dco-61-about-direct-capture-objectiveshttps://pdn.pega.com/dco-61-upgrading-older-versions-dcohttps://pdn.pega.com/dco-61-creating-discovery-mapshttps://pdn.pega.com/dco-61-creating-application-profilehttps://pdn.pega.com/dco-61-extending-document-wizardhttps://pdn.pega.com/dco-61-how-customize-application-document-templateshttps://pdn.pega.com/dco-61-sharing-and-merging-application-profileshttps://pdn.pega.com/dco-61-using-application-acceleratorhttps://pdn.pega.com/dco-61-using-application-document-wizardhttps://pdn.pega.com/dco-61-using-dco-application-enablement-wizardhttps://pdn.pega.com/dco-61-whats-newhttps://pdn.pega.com/dco-61-working-application-requirementshttps://pdn.pega.com/dco-61-working-application-use-caseshttps://pdn.pega.com/troubleshooting-hotfixes-61-sp2-direct-capture-objectives-are-available-self-servicehttps://pdn.pega.com/troubleshooting-hotfixes-61-sp2-direct-capture-objectives-are-available-self-servicehttps://pdn.pega.com/about-direct-capture-objectives-dcohttps://pdn.pega.com/dco-32-creating-application-profilehttps://pdn.pega.com/dco-32-enabling-dco-accesshttps://pdn.pega.com/dco-32-extending-document-wizard-templates


25/26

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" 5! 36!74 879 :6;;

https://pdn.pega.com/dco-32-using-dco-enable-application-wizardhttps://pdn.pega.com/dco-32-using-enterprise-application-acceleratorhttps://pdn.pega.com/dco-32-whats-newhttps://pdn.pega.com/dco-3231-using-application-document-wizardhttps://pdn.pega.com/dco-3231-working-application-requirementshttps://pdn.pega.com/dco-3231-working-application-use-caseshttps://pdn.pega.com/dco-release-noteshttps://pdn.pega.com/dco-31-creating-application-profilehttps://pdn.pega.com/dco-31-enabling-dco-accesshttps://pdn.pega.com/dco-31-using-enterprise-application-acceleratorhttps://pdn.pega.com/enhancements-direct-capture-objectives/enhancements-direct-capture-objectiveshttps://pdn.pega.com/how-add-entity-relationship-diagrams-and-screenshots-application-documenthttps://pdn.pega.com/how-add-application-details-application-document-wizardhttps://pdn.pega.com/how-build-screenshot-catalog-application-document-wizardhttps://pdn.pega.com/how-conduct-prep-and-review-style-dco-sessionshttps://pdn.pega.com/how-order-content-application-document-wizardhttps://pdn.pega.com/how-prevent-ie-warning-stop-running-script-when-adding-application-requirementshttps://pdn.pega.com/updating-customized-application-document-templates-server-side-document-generationhttps://pdn.pega.com/using-application-document-wizardhttps://pdn.pega.com/business-analyst-resources-overviewhttps://pdn.pega.com/using-pega-bpm-prpchttps://pdn.pega.com/using-pega-scrum-prpchttps://pdn.pega.com/dco-32-using-dco-enable-application-wizardhttps://pdn.pega.com/dco-32-using-enterprise-application-acceleratorhttps://pdn.pega.com/dco-32-whats-newhttps://pdn.pega.com/dco-3231-using-application-document-wizardhttps://pdn.pega.com/dco-3231-working-application-requirementshttps://pdn.pega.com/dco-3231-working-application-use-caseshttps://pdn.pega.com/dco-release-noteshttps://pdn.pega.com/dco-31-creating-application-profilehttps://pdn.pega.com/dco-31-enabling-dco-accesshttps://pdn.pega.com/dco-31-using-enterprise-application-acceleratorhttps://pdn.pega.com/enhancements-direct-capture-objectives/enhancements-direct-capture-objectiveshttps://pdn.pega.com/how-add-entity-relationship-diagrams-and-screenshots-application-documenthttps://pdn.pega.com/how-add-application-details-application-document-wizardhttps://pdn.pega.com/how-build-screenshot-catalog-application-document-wizardhttps://pdn.pega.com/how-conduct-prep-and-review-style-dco-sessionshttps://pdn.pega.com/how-order-content-application-document-wizardhttps://pdn.pega.com/how-prevent-ie-warning-stop-running-script-when-adding-application-requirementshttps://pdn.pega.com/updating-customized-application-document-templates-server-side-document-generationhttps://pdn.pega.com/using-application-document-wizardhttps://pdn.pega.com/business-analyst-resources-overviewhttps://pdn.pega.com/using-pega-bpm-prpchttps://pdn.pega.com/using-pega-scrum-prpc


26/26

U&" 5993;4 !!< :=:!!=;

Australia" 56! :=

• CONTACT US

• PRIVAC ! S"CURIT

• T"R#S OF US"

• US $ "U SAF" %AR&OR

• TRA'"#AR(S

)*+,- Pe.asystems Inc/
https://pdn.pega.com/contact-ushttps://pdn.pega.com/privacy-securityhttps://pdn.pega.com/pdn-terms-usehttps://pdn.pega.com/us-eu-safe-harbor-policyhttps://pdn.pega.com/trademarkshttps://pdn.pega.com/contact-ushttps://pdn.pega.com/privacy-securityhttps://pdn.pega.com/pdn-terms-usehttps://pdn.pega.com/us-eu-safe-harbor-policyhttps://pdn.pega.com/trademarks

Documents

creating application.docx