Skip to main content

Celonis Product Documentation

Configuring settings for the object-centric Open Credit Memo app

Use the Open Credit Memo app’s Settings view to configure the app’s runtime variables. The values that you set for the runtime variables are used for the Knowledge Model variables in the Open Credit Memo app’s Knowledge Model.


After you publish an app for the first time, changing runtime variable values in Studio doesn’t change their values in Apps. The Open Credit Memo app needs to be published right away to create the augmented attributes. So you’ll need to work with the views in the Apps area in order for the values of the settings to be applied for end users. It’s best to keep the two sets of variable values in sync so that your results in Studio match those in Apps.

For the Open Credit Memo app, the runtime variable values are used to calculate the realized value for credit memos. Value Realization and Prioritization for the object-centric Open Credit Memo app explains what each runtime variable is, how it is used in the calculations, and what KPI contains the calculation.


For the Open Credit Memo app, if you change the runtime variables when the app is in use, the realized value changes for all credit memos, including those handled and resolved in the past. The app does not keep a log or history of realized value. Before you change the runtime variables, make a note of the existing realized value if you need to know what it was.

Here’s how to work with the Settings view in Apps:

  1. In the Celonis navigation menu, select Apps.

  2. Find the Open Credit Memo app in the left navigation.

  3. Expand the app’s structure using the arrow, and select the Settings view.

  4. Update the values of any variables that you need to. If you haven’t selected a value, the app is using the default value.

  5. When you’ve finished configuring the settings, make the same changes to the settings in the Studio package for the app, to keep them in sync.


When you’ve finished setup and the app is in use by business users, to avoid accidental changes, consider limiting the availability of the Settings view. You could restrict it to a specific group of business users who are responsible for making adjustments to the variable values.