Saved formulas
Saved formulas are a useful tool to save PQL statements. The saved formulas may be also be used by other analysts in the analysis.
Manage saved formulas
 |
Access the saved formulas in the analysis settings.
To create new saved formulas add them with the button 'Create formula'.
Search the existing list of saved formulas.
To edit or view the saved formula click on the list entry.
Create saved formulas
 |
Set a name for the saved formula. This name will be shown in the data chooser, formula editor and function library of the visual editor.
Create a description for the formula. This description is available for the analysts in the function reference.
Add parameters to abstract parts of your formula and make them adjustable. More on parameters follows in the next section.
Define the formula statement you want to save.
You an access the full formula editor for easier formula creation.
Cancel or save your actions. Only on save new saved formulas will be stored.
Formula statements
All PQL statements supported in the Celonis analyses can be stored in a saved formula.
The only exception are variables. Variables are not supported in saved formulas!
To apply variables within saved formulas, read the next section.
Apply saved formulas in the analysis
Saved formulas can be used in all formula inputs in the analysis.
Syntax
KPI("<Name of the saved formula>" [, '<Parameter Input>']) Fast access to the saved formulas is provided with:
The data chooser
 |
The library in the visual editor
 |
The PQL reference
 |
Parameters
Parameters allow you to abstract a part of the saved formula's statement and the parameter will provide a type specific input in the visual editor. The end user re-using the saved formula in a component has to set the input for the parameter you defined either in code or in the provided input block of the visual editor. Parameters are set on the saved formulas by putting the parameter's placeholder, e.g. {p1} into the formula. The following parameter types are available:
Parameter type text
Saved formula
 |
Applied in Visual Editor: Input B will replace {p1} on the formula statement.
 |
Applied in Code Editor: B will replace {p1} on the formula statement.
KPI("Ratio of Users", 'B')Parameter type integer
Saved formula
 |
Applied in Visual Editor: Input 100 will replace {p1} on the formula statement.
 |
Applied in Code Editor: 100 will replace {p1} on the formula statement.
KPI("Ratio of Users", 100)Parameter type decimal
Saved formula
 |
Applied in Visual Editor: Input 1.0 will replace {p1} on the formula statement.
 |
Applied in Code Editor: 1.0 will replace {p1} on the formula statement.
KPI("Ratio of Users", 1.0)Parameter type condition
Saved formula
 |
Applied in Visual Editor: Usertype equals B will replace {p1} on the formula statement.
Orignial state:
 |
With input values:
 |
Applied in Code Editor: "_CEL_P2P_ACTIVITIES"."USER_TYPE" = 'B' will replace {p1} on the formula statement.
KPI("Ratio of Users", "_CEL_P2P_ACTIVITIES"."USER_TYPE" = 'B')Parameter type column
Saved formula
(optionally a default value for the selected column can be set)
 |
Applied in Visual Editor: The selected column via the available dropdown will replace {p1} on the formula statement.
Initial state:
 |
Selected columns:
 |
Applied in Code Editor: "_CEL_P2P_ACTIVITIES"."USER_TYPE" will replace {p1} on the formula statement.
KPI("Ratio of Users", "_CEL_P2P_ACTIVITIES"."USER_TYPE")Parameter type activity name
Saved formula
 |
Applied in Visual Editor: The selected activity via the available dropdown will replace {p1} on the formula statement.
Initial state:
 |
Selected activity:
 |
Applied in Code Editor: 'Change Price' will replace {p1} on the formula statement.
KPI("Custom activity ratio", 'Change Price')Parameter type table
Saved formula
(optionally a default value for the selected table can be set)
 |
Applied in Visual Editor: The selected table via the available dropdown will replace {p1} on the formula statement.
Initial state:
 |
Selected table:
 |
Applied on Code Editor: "_CEL_P2P_ACTIVITIES" will replace {p1} on the formula statement.
KPI("Custom Count Items", "_CEL_P2P_ACTIVITIES")Parameter type date and time
Saved formula
 |
Applied on visual editor: The selected timestamp will replace {p1} on the formula statement.
 |
Applied on Code Editor: 2017-12-6 8:56:45:00 will replace {p1} on the formula statement.
KPI("Datediff against eventlog", {d '2017-12-6 8:56:45:00'})Combine parameters and variables to adjust formulas from the analyses frontend
 |
 |
 |
You can use a combination of dropdown buttons and the saved formulas to allow users with only view rights to adjust what KPI they are shown in a chart or table. The following example will showcase how you can set up the Rework Ratio to be dependent on the activities selected by the user:
Create a saved formula with a text parameter to replace the activity names in your case when statement.
Input the saved formula's KPI statement with the variable name input to the parameters value.
Create a dropdown that writes to the variable.
Now selecting multiple or a single value on the dropdown will change the calculated value accordingly.