Skip to main content

Celonis Product Documentation

Editing views for the object-centric Duplicate Invoice Checker

The Duplicate Invoice Checker comes with a prebuilt set of views. The Duplicate Invoice Checker’s only user-visible view is the Action View. The base views and embedded views are available for editing through it.

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 attributes or relationships that you added to the Celonis object types used in the perspective_DuplicateInvoiceChecker_DuplicateInvoiceCheckerApp perspective.

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.


The Duplicate Invoice Checker relies on the VendorAccountItem object type, which is a Celonis object type supplied with the dedicated perspective for this app, perspective_DuplicateInvoiceChecker_DuplicateInvoiceCheckerApp. To create it, we combine the VendorAccountCreditItem and VendorAccountDebitItem object types from the standard Accounts Payable perspective. VendorAccountItem only contains the attributes that are part of those Celonis object types as supplied - it won’t contain any custom attributes that you added to extend those object types.

It’s possible to add custom filters in the Duplicate Invoice Checker's Action View to hide groups that contain a specific type or combination of documents. It's better to exclude documents from checking by pre-filtering them in the AI Annotation before they appear in the results, because then you haven't wasted resources. Post-filtering in the Action View is useful as a backup if you don't want to reset the result table or modify your backend settings, or if you want to handle a false positive that only comes up occasionally. Configuring the AI Annotation for the object-centric Duplicate Invoice Checker explains how to set the standard filter dimensions and how to add custom PQL filters to remove documents from checking.

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.

Here’s how to edit the Duplicate Invoice Checker’s Action View:

  1. In the Celonis navigation menu, select Studio.

  2. Find the Duplicate Invoice Checker in your Studio space navigation.

  3. Expand the package’s structure using the arrow, then expand the folders to find and select the view you want to edit.


    • Base views contain the common components for multiple other views. When you change something in the base view, it changes everywhere that view is used. Other views can reuse part or all of the base views, adding, editing, or removing components. This is called extending the base views.

    • Embedded views are contained in other views. They can be used directly in a base view and embedded in each other.

    • Profile views contain details or lists for a particular item. These views open when the user selects an item.

  4. In the view, click Edit Mode or press Ctrl + Shift + E to enter edit mode.

  5. Click the Edit Component button on any component 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.

  6. When you’ve finished editing a component, click Save to save and exit.

  7. When you’ve finished editing all the components you want to, click Save to save the view, then click Exit Edit Mode to lock it again.


    It’s also possible to edit views in the YAML editor if there’s something you can’t achieve in the visual editor. Click the Switch to Code Editor icon </> to view the YAML.

  8. When you’ve finished editing all the views you want to, publish a version of the app package. There's a Publish Package button at the top of all the screens in your Studio space.