To create your application, follow these steps.

Step 1: Application Settings

Fill out the following fields on this panel.

1. Application — Enter a name for your new application. It must start with a letter and use only letters, digits, ampersands, underscores, and dash characters. The name may contain spaces. This text appears in the application form's Short Description label. Choose a name that is unique in the entire PRPC system.
   
   This name is concatenated and used for the application record's Name key part, class layer, and RuleSets. If the concatenated name exceeds eight characters, the system truncates it to create a short name, which is displayed as a link beneath the field. If you want to edit the default name, click the link to open the Application Short Name dialog. Enter a name no greater than 14 characters. By default, the application version is 01-01-01.
   As a best practice, keep the name as short as possible to prevent exceeding class structure character limits as you extend your application.
2. Description — Optional. Enter a high-level description of this application. For example, the description answers the questions "What purpose does this application provide to our organization?" After your application has been created, you can view or modify the description in the Full Description field value on the application rule's History tab or the Application Overview landing page.
3. Built-on Application — Choose an application upon which you want to build the application. Select an item from the list, for example:
   • PegaRULES — Select to build a base PRPC application, which consists of the PRPC system's built-in classes and rules necessary for processing cases and other work.
   • PegaDM — Select to build a base PRPC application with decisioning features.
   • [Framework Name] — Select the name of a framework application in your enterprise that contains the rules and data objects you want to extend in your project. The Built-on Application drop-down list includes all of the frameworks available in your system. When you select a framework that has more than one version available, the system selects the highest.
     
     The checkbox Do not show this application as a built-on choice in App Express on the Application rule's Documentation tab must be empty in order for an application to appear in this list. When you create a framework in Application Express, the checkbox is empty by default.
4. Application Structure — Select one of the following:
• Framework and Implementation to create both an implementation application and its implementation class layer , and a new framework application and its framework class layer. In general, the best practice is to create both layers to allow for future growth and reuse.
• Framework only to create only a framework application and class layer.
• Implementation only to create only an implementation application and class layer.
  
5. Organization — Default is name of the organization specified in your user ID. You can do one of the following:
• Keep the default.
• Choose an organization (from an unlocked RuleSet version) in the auto-complete field.
• Enter a new name to create an organization. It must use alphanumeric characters, starting with a letter. It may contain spaces. A typical organization name is its stock ticker. The organization name cannot be the same name as the Application Name. This text appears in the organization form's Short Description label. This name is concatenated and used for the organization record's Name key part, the organization class layer , and RuleSets.
  
  If the concatenated name exceeds four characters, the system truncates it to create a short name, which is displayed as a link beneath the field. The short name provides the names for the class layer and RuleSets (not the organization record). If you want to edit the short name, click the link to open the Organization Short Name dialog. Enter a name no greater than six characters.
  
  If you are logged onto the system as [email protected], you must create an organization.

Click the Next button to advance to Step 2.

Click Advanced Configuration if you want to you to modify the settings created in Step 1. This facility allows you to modify the default implementation and framework application names and class names, create reusable division and organization unit class layers, or specify a project methodology. See   Application Express — Advanced Configuration . This topic also describes how to import built-on application assets when importing case types.

Step 2: Business Objectives

Enter items that define the expected business outcomes and objectives for the new application. After your application has been created you can view or modify business objectives on the Application Overview landing page or on the application rule.

The business objectives of the built-on application appear here by default.

Click the Next button to advance to Step 3.

Step 3: Case Types

Use this step to create case types when building a base application on PegaRULES or PegaDM, or import case types when building on a framework.

Building on a framework

If you are building an application on a framework, select the case types that you would like to use in the new application. By default, all are selected. The list includes case types that match one of the following qualifications:

• All top-level case types from the built-on application.
• Sub-case types that have the include case types in the create menu checkbox selected on the built-on application form's Cases and Data tab.
• Any other work types listed on the built-on application record that don’t have a corresponding case type rule defined.

Each case type displays its case type icon (as defined on the Case Designer Details tab), the class rule's label, and the Description text in the Case Type rule form's History tab. When Application Express generates the application, the selected case types and all of their sub-case types are copied over.

Optionally, expand the Additional Built-On Applications section to select case types inherited from any other built-on applications.

The import process includes all sub-case types belonging to the selected top-level case types.

The starting processes defined in the built-on application's case type rule's Starting Processes array appear in the imported case type rule. These processes are not imported into your new application but are referenced by it. You can run them from your application or copy them for specialization.

You can also import case types from the Cases Explorer in your new application.

Building a on PegaRULES or PegaDM

If you are building a base application on PegaRULES or PegaDM, complete the following required fields:

• Case Type — Enter a name that starts with a letter and use only letters, digits, ampersands, underscores, and dash characters. The name may contain spaces and cannot exceed 40 characters. After you generate the application, the name appears in the Description labels on the Case Type and Class rule form headers. The system concatenates the name to create the class rule's Class Name key part, and the case type's Applies To key part. See Class Rules — Completing the Create New or Save As form for details.
• Description — Enter a brief description of this case type. The text is used for the Case Type record's short description and populates the Full Description field on the form's History tab. The text appears when you use the Import case types option on the Cases Explorer, or when importing case types in Application Express.

Click Add Case Type to add another row.

You can also add case types from the Cases Explorer in your new application.

Click the Next button to advance to Step 4.

Case Type Conflicts/Warnings

When you click Next in Step 3, a dialog appears that displays error or warning messages if any of the following conditions is met:

• The name of the selected case type causes the name of the corresponding class to exceed 56 characters. To resolve, rename the case type in the edit box or edit the name of its parent classes or class groups in the tree.
• There are class name conflicts (class name of a case type is same as that of another case type). For example:

Framework class name	New class name	Conflict?
[PegaFSIF-Work-ComDep]	[PegaFSIF-Work-ComDep]	yes
[PegaKYC-Work-ComDep]	[PegaFSIF-Work-ComDep]	yes
[PegaFSIF-Work-ComDep]-Student-Aid	[Org-App-Work-ComDep]-Student-Aid	no

Where brackets [] indicate a class group.

To resolve, rename the leaf part of the case type in the edit box.

• If the built-on application has multiple class group that have a leaf node -Work, Application Express generates sub-class groups in the form <default class group> + <Grp 1,2,3...> to uniquely identify them. For example:
  

Framework class name	New class name
[PegaFSIF-Work]-Visa	[Org-App-Work-Grp1]-Visa
[PegaKYC-Work]-Master	[Org-App-Work-Grp2]-Master

Where brackets [] indicate a class group.

If you do not wish to keep the default names, rename them in the edit boxes.

Click Next when you are finished reviewing or making your updates in the dialog.

Step 4: Data Objects

Use this step to:

• Create data objects when building an application on PegaRULES or PegaDM, or import data types when building on a framework.
• Preview the application that will be generated.
• Create the application.

Building on a framework

If you are building an application on a framework, choose the data objects that you would like to use in the application. Application Express does not generate new data classes; it creates links between the new applications and selected data classes.

Optionally, expand the Additional Built-On Applications section to select data objects inherited from any other built-on applications.

You can also reuse data objects in your built-on applications by selecting the objects from your new application's Data Explorer .

Building on PegaRULES or PegaDM

If you are building a base application on PegaRULES or PegaDM, complete the following fields in order to create new data classes and links between the classes and the new applications.

Name — Enter a name that starts with a letter and includes only alphanumeric and dash characters. The name may contain spaces and cannot exceed 40 characters. After you generate the application, the name appears in the short description label on the Data Class form header. The system concatenates the name to create the property rule's Property name key part. See Properties — Completing the Create or Save As form for details.

Description — Enter a brief description of this data object. The text populates the Description field on the Class rule form's History tab, and appears when importing data types in Application Express.

Reuse Layer — Select the class layer the data object will belong to.

Click Add Data Object to add another row.

Preview the application

Before you create your application, click Preview to open a Preview screen that displays the records that Application Express will generate. These include the classes in each layer, their applications, and their RuleSets. The framework and implementation layers are determined by the settings in Step 1. Also displayed are the parent classes that the new classes directly inherit from. Data instances that do not have an Applies To class such as access group , operator ID, work group, access role, workbasket, and organization are grouped at the bottom of the dialog.

Click Close Preview to exit the dialog and return to Step 4. Revise your configuration based on the results, if necessary.

Create the application

When you have completed your configuration, click Create to generate your application (and if selected, a reusable framework). The system generates the necessary elements that seed the initial application.

When processing is complete, Designer Studio refreshes — the newly created application becomes the current application and the Application Overview landing page appears on the Home page. If you have created an application as [email protected] you must log off and log back on as one of the standard operators generated by the system.

Other records

In addition to the above, Application Express creates records as described below.

For each case type you add in Step 3 (when building your application on PegaRULES or PegaDM), Application Express creates the following:

• Class — A case type class in the work pool you are extending; inherits from Work-Cover-.
• pyDefault case type record — The default short description is the text you entered in the Description field on Step 3.
• pyStartCase flow — The flow is listed as the default starting process on the case type record's Processes tab. The flow is used by the first stage in a case lifecycle management design to create the case and initialize stage processing. The default short description is Create <case type short description> Case. This name appears in the Create menu on Case Designer and Case Manager portals.
• pyCaseManagementDefault work parties — Copied from the Work-Cover-.pyCaseManagement instance. By default, this value populates the Work Parties field on the flow form's Process tab.

Note the following:

• Organization, Division, or Unit data instances are not generated if they already exist in the system.
• Division and Unit class layers are created only if you define them in the Organization Settings area in the Advanced Configuration dialog.
• Default operators are created only if you select the Generate test operators checkbox in the Advanced Configuration dialog.
• When building on a standard Pega application, Application Express:
  • Creates the pyGeolocationTrackingIsEnabled when rule at the lowest application layer generated (for example, at the framework layer if also generating an implementation layer). This enables geolocation tracking for every case type in the application. See geolocation tracking.
  • Adds the UI Kit ruleset (UI-Kit-7) to the Application Rulesets list on the application form's Definition tab.