Creating an application setting
Create an application settings rule for all deployments of your system, customized by production level.For example, you can define a time-out interval that is consistent for all production deployments and another time-out interval that is consistent for all test deployments.
In the header of Dev Studio, click.
On the Create form, enter values in the fields to define the context of the application setting.
In the Label field, enter text that describes the purpose of the setting. The label that you enter is used as the default name for the setting, with spaces and special characters removed. This default name can be overridden as described below.
To change the default name for the application setting, click Edit, and then provide a unique value in the Identifier field. The name must start with a letter and use only numbers and letters, without spaces.
In the Owning ruleset field, enter the domain for the application setting. Despite the field label, this value does not have to equal a ruleset name; it functions as a namespace.
In the Add to ruleset field, select the name and unlocked version of a ruleset that stores the privilege.
Click Create and open to open the application settings form.
In the Category field, press the Down arrow key, and then select a category from the list.If you do not specify a category, the application setting displays under the Uncategorized category in the Application settings landing page in App Studio.For more information, see Categorizing application settings.
In the Value type field, select a value type from the list. The value type you select defines how the application setting is rendered in the Application settings landing page in App Studio. For example, if you choose Boolean, the application setting displays as a Boolean value.
Define application settings values by production level. For more information, see Defining production-level application setting values.
On the Display tab, perform one of the following actions:
- Select the Hide the setting in landing page check box to hide the application setting from the Application settings landing page in App Studio. If you leave this check box unselected, the application setting renders in the landing page when you save the rule.
- By default, every application setting uses the pzSettingDefaultViewInLP section to render the application setting in the landing page in App Studio. In the View for landing page field, press the Down arrow key to override the default section and select a new section.
- Reference application settings in rules
The pzsettingsORA UI control is a reusable control that you can use to reference application settings in any rule in your application. The control defines how the application settings appear in your rules. For example, you can configure the control to display only categories or remove the option to create a new application setting.
- Categorizing application settings
Create categories to organize your application settings to make it easier for users to search for application settings and understand their purpose. For example, if you create a category called Integration, you can apply this category to application settings that relate to integrating with customer data.
- Defining production-level application setting values
Configure separate values for different production levels. At runtime, the system uses the application setting value that corresponds with the current production level.
- Configuring application settings
Application settings rules define run-time settings that can differ based on a system's production level, and which are resolved at run time through rule resolution. Application settings are identified by name and owning ruleset. The owning ruleset functions as a namespace and does not have to equal the ruleset that contains the rule.
- Viewing application settings
You can view, search for, and edit application settings by using the Application settings landing page in App Studio. The landing page displays the application settings that correspond to the current production environment that you are using.
- Copying a rule or data instance
Use the Save As form to copy an existing record's functionality to a new record with unique key parts. This form is pre-populated with the original record's key parts and creates default values for the new record's context.
- Creating a specialized or circumstance rule
You can create a specialized or circumstance rule to create a variant of the rule that can be triggered only conditionally. The created rule is resolved and active only when the specified conditions are met. Create specialized or circumstance rules to address dynamic business requirements without changing the core logic every time. For information about rule resolution exceptions and how they might affect circumstance rules, see .