Celonis Product Documentation

Enhanced View variables allow you to centrally create and manage information that is referenced and reused across components within the same View. You can use enhanced View variables in buttons, KPI lists, tables, and input dropdowns.

To create enhanced View variables when editing your View:

Once saved, your enhanced View variables are then displayed in the variables menu within that View only.

To edit or delete an existing variable, click Edit:

Enhanced view variables can also be seen in the PQL editor, accessed when editing View components that use data:

Enhanced Knowledge Model variables allow you to centrally create and manage information that is referenced and reused across Views where that Knowledge Model is in use. Like with enhanced View variables, you can use enhanced Knowledge Model variables in buttons, KPI lists, tables, and input dropdowns.

Enhanced Knowledge Model variables are created using the PQL editor. To access the PQL editor and created enhanced Knowledge Model variables from within a View:

1. Open the PQL editor using View components where data fields can be selected:

   1. Either: Click the PQL editor button directly.

   2. Or: Add data to a setting (such as a table column)

2. Locate the Knowledge Model variable section and click Add:

3. Enter a variable name, select a variable type, and optionally enter a description.

   • Key: This should be a unique ID, allowing for the variable to be referenced across components. Avoid using special characters here.

     Your variable key can then be referenced in your View as:

     ${KEY}

   • Type: Choose between string (text), number (#), boolean (true /false), and object.

     For object variables, see: Using enhanced variables for object types

   • Default Value (optional): This is the value that will be referenced unless otherwise stated.

4. Optional: Enable Advanced Options and enter a variable description and choose the variable and user scope.

   • Description: Provide further information here, giving your team added context where needed.

   • Variable Scope: Choose whether this variable is saved at a View level only, within the knowledge model (which can be referenced by all Views created using that model), or for all assets within the existing package.

   • User Scope: Choose whether this variable is specific to your account or is available for all users within your team.

5. Click Save.

Once saved, your enhanced Knowledge Model variables are then displayed in the variables menu for all Studio assets that use this Knowledge Model.

To edit or delete an existing variable, click Edit:

Once created, you can reference enhanced variables in the following View components: buttons, KPI lists, tables, and input dropdowns.

Enhanced variables can either be added through the Interaction settings for components, such as with a KPI list:

Alternatively, enhanced variables can be referenced in PQL expressions using the following format:

${KEY}

Input boxes allow you to record a manually entered value from users and then use that value throughout your View. This saves the input as either a View variable or a Knowledge Model variable. This variable can then be used in other components to adjust the View based on the manual value entered by the user.

In this example, the input box allows users to enter the minimum net value:

This input box example is configured by saving the user input as a Knowledge Model variable. In this case, the variable is a number type:

${minimum_value_threshold_unbilledcurrency)

This variable can then be used in other components, such as a text box:

With the published version of the app showing the value entered (10):

Enhanced variables for object types allow you to store the metadata of a particular metric or attribute in one single variable. This enhanced variable can then be reference in View components such as input dropdowns, text boxes, and component fields.

The schema (i.e structure) for enhanced object variables is generated when a default value or a current value is set and follows the JSON syntax. As such, you need to define key-value pairs.

For example:

{
"key1": "String",
"key2":123,
"key3":true
}

This is then added to the Default Value field when creating or editing the object variable:

Enhanced objects variables are then referenced in the following ways: