  Application Express — 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 check box 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 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 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.
For each case type you add, 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.
You can also add case types from the Cases Explorer in your new application.
Using extension points to import case type records
You can use extension point activities to automatically import rules and data records from built-on applications when you add case types using Application Express, or when you use the Add or Import (case type) commands in the Cases Explorer.
Case Type Conflicts/Warnings
When you click Next, a dialog appears that displays error or warning messages if certain conditions are met.
About Application Express