Skip to main content

You can now create and use enhanced variables in your Studio content. Enhanced variables allow you to centrally create and manage information that is referenced and reused across components and assets in Studio. They act as placeholders for information, either based on dynamically inserted context (such as company names, countries, and sales orders) or with manual input by the app user (such as entering the cost of an item).

There are two types of enhanced variables:

  • Enhanced View variables: These are specific to individual Views and can't be reused across Views in the same package.

    To learn how to create and manage enhanced View variables, see: Creating and managing enhanced View variables.

  • Enhanced Knowledge Model variables: These can be used wherever the Knowledge Model is being used, as such can be reused across Views, Packages, and Spaces.

    To learn how to create and manage Knowledge Model variables, see: Creating and managing enhanced Knowledge Model variables.
     

    In addition, you can now view and manager your variable state while editing your View. The variable state represents the current value of the variable for the user. Initially, this is the default value, but it may change when the user interacts with the application.
     


    Existing Knowledge Model variables

    What were previously referred to as 'Knowledge Model variables' are now known as 'Legacy Knowledge Model variables'. These legacy Knowledge Model variables can only be used when creating legacy Studio Views.

    You can continue to create and manage your legacy Knowledge Model variables directly in the Knowledge Model:
     

    For more information about legacy Knowledge Model variables, see: Variables (legacy views only).

     

Could you provide me information of using the interactions settings in a KPI list with a enhanced variable please?


Hi,
sure. After you have created an enhanced variable, you can use a KPI list component to set the value of the enhanced variable. At the moment you can write the ID, name, or the full meta-data back to your variable. To do this:
1) Add a few KPIs to your KPI list
2) Add interactions and choose a variable where you want to write the value into
3) Select for example the ID
4) save the view and go into interaction mode.
5) Now, by clicking on a KPI in the list, it will write the name of the KPI back to the variable.

This is helpful for example when you want to create Views which react to user input.

Let me know if this helps.
 


Thank you Timothy,

In the example we use the KPI ID, what happens if we use the name or the metadata? what output would appear in the variable?

 


For the name: You write back the name
For the ID: you write back the ID
For metadata: You write back the full metadata behind the variable as captured in the KM. This is mainly for advanced use-cases.

Example of KPI meta-data:

{"aggregation":true,
"displayName":"AAAA",
"id":"194f0726-8c13-41ec-932e-bafc01e39013",
"pql":"KPI(\"aaaa\")",
"shortDisplayName":null,
"referencedEntity":{"id":"aaaa","type":"KPI","columnType":"int"},
"breakdowns":[],
"aggregations":[],
"parameters":[],
"targets":[],"type":"KPI",
"unit":null,
"format":null,
"defaultTarget":null,
"isCustomTargetDisabled":null,
"allowTargetUpdate":true,
"desiredDirection":"NONE",
"priority":false,
"benchmarking":null,
"filterIds":null,
"description":"asdfasdfasdfa",
"customAttributes":null,
"columnType":"int",
"internalNote":null,
"autoGenerated":null,
"scope":null}