Skip to main content
This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.
LinkedIn
Copied!

Creating applications with the New Application wizard

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.

Beginning with Pega 7.2.2, this version of the New Application wizard has been deprecated and renamed the Legacy New Application wizard. For information about the updated New Application wizard, see New Application wizard.

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.
    Application menu
  2. Click Create new application to start creating an application.

    Step 1: Application Settings displays and contains default values.
    Step 1: Application Settings

Step 1: Application settings

Specify the following application settings:

After you create your application, you can view or update the description on the Application Overview landing page in Designer Studio.
  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 is displayed under the Application field.
    Step 1: Application Settings with Description field.
  3. To change the short name, click the name to open the Application short name modal dialog box.
  4. 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.

    Specifying the application description

  6. Review the values in the following fields:
    • 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.
      Specifying the organization as 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.
    Advanced configuration modal dialog box
  2. Select the Generate reusable division records check box. This setting displays the Division layer field in the Class structure - Implementation layer section.
    Specifying organization settings

    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.

Specifying business objectives

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 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 imports only 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 3: Case Types

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, use all the data objects, so do not clear any of the check boxes.
Step 4: Data Objects

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.
    Previewing your new application
  2. Expand Cambridge Purchase Request Implementation Layer to display the classes and the ruleset names.
    Previewing the implementation layer
  3. To preview the case types in the application's work pool, expand Work (Default Work Pool).
    Previewing case types
  4. 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 can now 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.
    Application Overview landing page

Related Content

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us