The New Application wizard Advanced Configuration dialog allows you to manually configure or override default settings made by the system or entered by you in Step 1.
Field |
Description |
Application Rule Name |
The application rule Name key part. By default, this is the name you entered in Application field on Step 1 (spaces are removed). Changing the rule name value does not update the Application field. If you return to Step 1 and update the Application field, the rule name is updated in this field. |
Application Version |
The implementation application version default is 01.01.01 |
Project Methodology | A project methodology associated with the new application. The default is Scrum . Your selection appears on the application rule's Definition tab. See Pegasystems methodologies. |
Built-On Application |
The application selected in Step 1. Changing this value will change the case type and data object settings in Steps 3 and 4, respectively. |
Built-On Version | The highest version of the application you entered in the Built on Application field on Step 1. Cannot be edited. |
Application Structure |
Select:
|
Framework Name |
Visible if you select Framework and Implementation or Framework only. Specify the application framework application Name key part. By default, the system uses the Application Rule Name and appends This setting does not alter the framework class name tha appears in the Class Structure - Framework area. |
Framework Version | The framework application version default is 01.01.01 |
Enable Pega API access for application administrators | Allows the application administrator access to the Pega API by adding the PegaRULES:PegaAPI role to the Admin access group. |
Note: As a best practice when creating division and unit class layers, use names between four to seven to characters. Due to the 56 character class name limit, keeping layer names short enables you to provide descriptive case and data type names.
Field |
Description |
Organization Name |
The name provides the Organization Name key part for the application's organization, division, and organization unit rules. The value entered in the Organization Name field on Step 1 is the default. The system also uses this value for naming classes in the organization reuse layer. Example If you enter the organization name
Use auto-complete to select an existing organization if you want to reuse the organization's class structure, rules, and data records in your implementation and framework applications. Enter a name if you want to create a new organization and organization layer. If you are creating an organization, you can modify the default organization Class Name key part in the Class Structure - Implementation area on this dialog. |
Create a reusable division layer | Select to extend the organization class layer to create a division class layer. Available only if you enter a value in the Division field. |
Division |
The Division key part of a division rule. If you added a new organization in Step 1, the system enters If you selected an existing organization, use auto-complete to select a division in that organization or enter a new division name. If you select Create a reusable division layer, the system by default concatenates the organization and division name to create the division-layer class names. For example, if |
Create a reusable unit layer |
Select to extend the division class layer to create a division class layer. Appears if you select Create a reusable division layer. Available only if you enter a value in the Unit field. |
Unit |
The Unit Name key part of an organization unit rule. If you added a new organization in Step 1, the system enters If you selected an existing organization, use auto-complete to select a unit in that organization or enter a new unit name. If you select Create a reusable unit layer, the system by default concatenates the unit name with the organization name and division name to create the unit-level class names. For example, if The system appends the unit name to the organization name to generate a ruleset named |
Create test operators? |
Available only if this is a new organization. Select to automatically create the standard operator IDs for that organization. The operator IDs are Administrator@orgname, Manager@orgname, and User@orgname. When generating the application, the system creates the operator IDs with the standard access groups to access the new implementation and framework applications. Enter a password if you do not want to use the default value rules. |
Field |
Description |
Organizational Layer |
Displays the default organization layer class name based upon your Organization Name selection. If you are creating an organization, you can change the Class Name key part in this field. |
Division |
Appears if you selected Create a reusable division layer. Displays the default division layer class name based upon your Division selection. You can change the Class Name key part in this field. |
Unit |
Appears if you selected Create a reusable unit layer. Displays the default unit layer class name based upon your Unit selection. You can change the Class Name key part in this field. |
Application Layer |
Displays the implementation class layer's name. This value is also used for the ruleset name associated with the application and classes. The default is the Application Name value (spaces removed) entered on Step 1. You can change the Class Name key part in this field.
MyCo . If you enter AutoLoan :
|
Class Group |
Displays the class group (workpool) name. |
Appears if you selected Framework Only
or Framework and Implementation
in the Application Structure field. Displays the default framework layer class structure.
The framework Class Name key part (concatenated with the organization class name and the base framework class name FW
); and classes. By default, the system appends FW-
to the Application Rule Name value.
Example
Assume the organization name is MyCo
. If the application name is AutoLoan
:
AutoLoanFW
MyCo-FW-AutoLoanFW
, MyCo-FW-AutoLoanFW-Work
, MyCo-FW-AutoLoanFW-Data
,and MyCo-FW-AutoLoanFW-Int
FW
and AutoLoanFWInt
You can update the Application Layer and Class Group Name names to suit your requirements. The system automatically appends FW
to the name. These fields are useful if you want your implementation and framework applications to have different class structures.
Click Save to keep your updates, close the dialog, and return to Step 1.