Editing views for the object-centric Payment Term Checker app
The Payment Term Checker app comes with a prebuilt set of views. Edit the app’s views in Studio if you need to:
Make any customizations and changes to suit your business process.
Change the look of the supplied views.
Include custom items that you added to the perspective that you’re using with the app.
The app doesn’t do anything automatically with customizations to Celonis object types - they won’t be surfaced in views. If you want to use them, you’ll need to edit the app’s views to include them. You don’t have to surface all (or any) of your custom attributes and relationships in the app’s views. If you don’t, it doesn’t cause a problem, the app just ignores them.
These views for the Payment Term Checker app are directly accessible to users, and linked views are available for editing through them:
Getting Started - this view gives a brief overview into the app itself, its individual views, as well as some introduction to the use cases covered by the app.
Payment Term Mismatches - this is the main (operational) view that business users can use for their daily tasks, with the tabs Open Documents and Cleared Documents.
Value Tracking - this view follows up on your operational payment term mismatches and shows resolved or rejected payment term mismatches.
Payment Term Analytics - this view contains deeper analytical insights into the three main use cases of the app:
Value Framing - this view provides insights into the value of the three core use cases (Mismatches, Short terms, Unharmonized terms) and how much value can potentially be realized by improving payment terms.
Settings - this is a view where you can manage the values of runtime variables.
Payment Term Checker app - object-centric has more details of the tabs in each view.
Tip
In the new Studio experience, we keep a history of comments and other updates to augmented attributes. If you want to display these in a view, edit the view to add the Activity history component from the Object-specific details group.
You’ll need Analyst permissions for Studio and for the relevant views and components to modify them. If you need training, check out the training track “Build Knowledge Models and Views” on the Celonis Academy.
If you make any edits to view components that involve the calculated attributes from the Knowledge Model, we’ll automatically update the calculated attributes in the Knowledge Model to match your edits. You can also adjust them directly in the Knowledge Model before or after editing the views, as explained in Validating KPIs.
Here’s how to edit the Payment Term Checker app’s views:
In the Celonis navigation menu, select Studio.
In the Studio overview, find the Payment Term Checker app in the space where you installed it, and click its tile.
Expand the package’s structure, then expand the folders to find and select the view you want to edit.
In your selected view, click Edit View to enter edit mode.
Select any component of the view to go to the component editor. Here you can add and remove data fields shown in a table or chart, change sorting and display attributes, add action buttons, and make other edits, as relevant for the component type.
When you’ve finished editing a component, click the Save icon to save and exit.
When you’ve finished editing all the components you want to, click the Save icon to save the view, then click the Exit Edit Mode icon (the blue square with the X) to lock it again.
Tip
It’s also possible to edit views in the YAML editor if there’s something you can’t achieve in the visual editor. To view the YAML, click the View settings icon and select Edit View YAML.
When you’ve finished editing all the views you want to, publish a version of the app package. There's a Publish button at the top of all the screens in your Studio space.