Example 1: Define properties that can be accessed by all users of an application
Consider that you want to define a singular set of properties that affect all users who use the Task application. For example, you can define the following properties:
- AutoCloseCompleteTask (Boolean)
- AutoCloseDays (Integer)
- NotifySubmitterOnClose (Boolean)
These settings can be defined so that only the users having Task Config permission can access and populate these properties. The properties, in turn, influence the business process and application behavior. After you define the properties, users can access them in different ways such as on the Administration tab of BMC Helix Innovation Studio.
You can then define a process that searches for these settings and values, and follow different business processes based on the content. This makes the application data configurable.
The following image shows an example of settings for the Task application:
Example 2: Specify a set of properties that can be defined for each user of an application
Consider that you want to define ShowFullName (Boolean) property. After you define the setting, it can be repeated for multiple users for defining application settings stored at an individual user level, as shown in the following image:
Example 3: Specify a set of properties that can be defined and restricted based on data other than group
Consider that you want to define a property based on multiple types of a ticket priority. For properties that are repeated in Settings, you can define a parent-child relationship between the Settings, as shown in the following image. This means that you define a dependency of one Setting on another Setting.
Here, Setting 2 is configured as the parent Setting for the Urgency-based Setting, as shown in the following image:
