Configuring settings for the case-centric Shipped Not Invoiced app
Use the Shipped Not Invoiced app’s Validation and Value Assessment view and Settings view to configure the app’s runtime variables.
The Validation and Value Assessment view is a quickstart view for setup which guides you through the process of validating the business logic and making a value assessment for this use case. The parameters you set in this view are automatically changed in Settings and reflected in the Action View.
In the Settings view, you can change the currency variable for the frontend currency value (which defaults to euros, EUR), and all the other runtime variables, including those in the Validation and Value Assessment view.
The values that you set for the runtime variables in these views are used for the Knowledge Model variables in the Shipped Not Invoiced app’s Knowledge Models.
Important
After you publish an app for the first time, changing runtime variable values in the Validation and Value Assessment view or Settings view in Studio doesn’t change their values in Apps. The Shipped Not Invoiced app needs to be published right away to create the augmented attributes and augmented tasks and make profile views available. 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.
Here’s how to work with the Validation and Value Assessment view and Settings view in Apps:
In the Celonis navigation menu, select Apps.
Find the Shipped Not Invoiced app in the left navigation.
Expand the app’s structure using the arrow.
Select the Validation and Value Assessment view if you want to be guided through the setup process, or the Settings view if you know what you want to change.
Update the values of any variables that you need to. If you haven’t selected a value, the app is using the default value. Use the PQL query button to see the details for a KPI.
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.
Tip
When you’ve finished setup and the app is in use by business users, to avoid accidental changes, consider limiting the availability of the Validation and Value Assessment and Settings views. You could restrict these to a specific group of business users who are responsible for making adjustments to the variable values.