Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Creating configurations

Updated on January 14, 2022

Provide no-code tools for run-time administrators of your application by creating configurations. Configurations determine run-time behavior of your application that users can flexibly adjust to meet their unique business needs.

For example, in a financial application, you can create a configuration that displays currency rates for every case that case workers process. When the business objective changes, an application administrator can disable the configuration to hide the currency rates. For more organized management of your resources, you can combine configurations into configuration sets.
Before you begin: Create a configuration set to store your configuration. For more information, see Creating a configuration set.
  1. In the navigation pane of App Studio, click SettingsConfigurations.
  2. In the header of the Configurations section, click Add configuration.
  3. In the Create configuration dialog box, in the Name field, enter a name for your configuration.
    For example: Enter Currency rate.
  4. In the Description field, briefly describe the purpose of the configuration.
    For example: Enter Display currency rates for dollar to euro.
  5. In the Configuration set list, select the configuration set to store the configuration.
  6. In the Configuration scope list, define elements to which the configuration applies:
    • To apply the configuration to an entire application, select Application.

      The configuration can apply to assets in an entire application, such as data model, UI elements etc.

    • To apply the configuration to a specific case type, select Case type, and then select the case type that you want to use.

      The configuration can apply to assets related to a selected case type, such as a case type data model or views in the case type.

      Tip: You can also select all case types.
  7. In the Type list, select a type for the configuration.
    For example: For a configuration that either displays or hides currency rates, select Boolean.
  8. If you create a picklist, in the Add choices section, click Add choice, and then, in the text field, enter a value that users can select at run time.
  9. Optional: To add more choices for the picklist, repeat step 8.
  10. In the Default value list, select a default value for the configuration:
    Select a specific value
    1. Select Constant.
    2. In the value field, select or enter a default value for the configuration.
      For example: To display currency rates in cases for a Boolean-type configuration, select True.
    Calculate a value at run time
    1. Select Calculated value from decision table.
    2. In the list of decision tables, select a decision table that you want to use, or create a new decision table.
      For more information about decision tables, see Authoring decision tables in App Studio.
      For example: You can create a decision table that returns a loan limit for a customer based on the customer's income and account type.
      When you build a decision table, the system sources the columns for the table from the data model of the scope that you select for the configuration.
  11. Optional: To provide a unique ID for the configuration, expand the Advanced section, and then, in the ID field, enter a new value.
  12. Click Submit.
For example: The following figure shows a configuration that, by default, displays currency rates for cases of all case types within an application. At run time, an application administrator can disable the configuration to hide the currency rates.
Currency rates configuration
A sample configuration of the Boolean type to display currency rates at run time

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us