Skip to main content

Celonis Product Documentation

Creating and managing enhanced View variables

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.

For an example of using enhanced view variables, see: Enhanced variable use case example using an input box.

And for an overview of variable types, see: Enhanced variables.

To create enhanced View variables when editing your View:

  1. Click Variables - Create Variable:

    create_variables.png

  2. 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: ???

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

  3. 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.

    configure_variables.png

  4. Click Save.

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:

edit_existing_variable.png

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

view_variables_within_PQL.png
Enhanced variable use case example using an input box

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:

billing_relevance_variable.png

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)
example_of_input_box.png

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

variable_in_text_box_example.png

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

text_box_active_variable_example.png
Using enhanced view variables in PQL

To ensure that data and string type view variables are correctly interpreted and function as intended within PQL, please follow the guidelines below:

  • Date type variables: When you're comparing data type variables, the variable formatting to use is:

    {t ${date_variable_name_here}}

  • String type variables: When using string type variables, the variable formatting to use is:

    ('${string_variable_name_here}')

    Without quotations, the variable will be treated as if it is PQL. For example, a string variable value of 2025-02-01 without using quotations will result in a literal calculation: 2025-2-1 = 2022.

  • Date string variables: Data string inputs can be referenced in PQL using  {d } or integer inputs with a count of milliseconds since 01.01.1970 using {t }. Two formats are supported as date string input:

    • yyyy-MM-dd HH:mm:ss

    • yyyy-MM-dd

    For PQL examples of date string variables, see: DATE.