Skip to main content

I have created variables in my Knowledge Model (see YAML below) that I am trying to have input boxes to modify. On my View, when I create an Input Box and try name a variable I get an error that no variables exist. What am I doing wrong?

 

Bonus Question: In Views can I use those variables to create an Improvement Opportunity calculation similar to that of Analysis?

 

Knowledge Model Variable Definition:

 

variables:

  - id: input_me

    displayName: Input

    value: |

      5

*note I did not think I had to define a value, but I am required to in the visual editor

 

YAML for the Input Box:

 

id: input-box-6041fe8f-bff0-495d-844d-d1b0c8d7c721

type: input-box

settings:

  name: Input Box

  type: number

  onChange:

    update:

      variables:

        - name: <Input>

 

;note the error at the bottom of the screen says that no variables are available]

 

Hi,

 

For sure you can use runtime variable which will be accessible in both View and Knowledge Model. You can read about it here:

Package runtime Variables (celonis.com)

 

Maybe there is a different way but to be honest I am not aware of it

 

Good luck :)

 

 


Hi Timothy,

 

To make things simple, there are multiple types of variables, all with their different use cases:

 

  • runtime variables: use through the entire package (see example of Marcin above, Package runtime Variables (celonis.com))
  • view variables: use within views to change behaviour of the analysis, this elements will directly be updated (for instance, change chart dimension from months to quarters, Views Variables (celonis.com))
  • Knowledge Model variables: To use within the knowledge model itself, cannot be used within the views nor analyses, but only within KM KPIs/Filters (see Knowledge Model - Variables (celonis.com)).
  • Analysis variables: Can only be seen within Studio Analyses, mainly the same functionality as KM variables, but on a different place.

 

To see the variables that you can access within a view, press the variables button on top:

image 

 


Reply