Skip to main content

Celonis Product Documentation

Installing the object-centric Payment Term Checker app

The object-centric version of the Payment Term Checker app works with objects and events created for object-centric process mining. Before you set up the object-centric version of the Payment Term Checker app, you’ll need to enable and configure the Accounts Payable process, load the object-centric data model with your data, and validate the standard Accounts Payable perspective, perspective_celonis_AccountsPayable. See Prerequisites for the object-centric Payment Term Checker app

You can download the Payment Term Checker app from the Celonis Marketplace. When you link the Payment Term Checker app to the perspective_celonis_AccountsPayable perspective, it uses the objects and events that you’ve already built from your source system data and stored in the OCPM Data Pool.

Here’s how to install the Payment Term Checker app:

  1. Open the Celonis Marketplace from the Celonis navigation menu, and search for all or part of the app’s name. You’ll probably see an original case-centric version of the app as well as the object-centric version. Only the object-centric version is suitable for object-centric process mining.

  2. Select the Payment Term Checker (object-centric) app to see its information page.

  3. Select Get it now to install the app. If you see Request Access instead, click this to request the app, and check the other prerequisite steps in Prerequisites for the object-centric Payment Term Checker app.

  4. In Celonis, choose a Studio space to install the app in. You can use an existing Studio space or create a new one. (You can move the app after installation.) Click Confirm to proceed with the installation.

  5. In the Studio overview, find the Payment Term Checker app package in the space where you installed it, and click its tile to go to the app package.

  6. Click the Package Settings icon (the box) and select Variables.

  7. Select the Assign Data Model button, then search or browse for the perspective_celonis_AccountsPayable perspective and click to select it. Click Save to set the Data Model variable.

    Tip

    Don’t pick the version of the perspective with the prefix test: This is the version for the development environment, which won’t work - you need to use the production perspective without the prefix.

  8. The Payment Term Checker app needs publishing before configuration to create the augmentation tables. Select the Publish button to publish a version of the app.

    Tip

    To prevent business users from accessing the app while you’re working on setup, set the package permissions to hide it from them. Click the Package Settings icon (the box), and select Permissions. Set “No Permissions” to stop a user or group from seeing the app. You can also hide the view in the Apps Perspective tab in the package settings, but then you won’t see it either, so you won’t be able to check your settings in Apps.

  9. Open the view Payment Term Mismatches and validate that your data is shown. It might take a few seconds before all the tables are created. If you see “Table could not be found” errors, wait for a short time and then reload the page to see if they disappear. If they remain, you’ll need to fix this during app setup.

  10. Use the Settings view in the Configuration & Value Framing folder to set up the variables for the app to align with how things are done in your organization. See Configuring settings for the object-centric Payment Term Checker app.

    Tip

    Because the Payment Term Checker app needs to be published right away, you’ll need to change the settings in Apps as well as in Studio. Changing the settings in Studio after publishing doesn’t affect the values in Apps.

  11. If you need to make further changes that you can’t achieve using the app settings, you can make your own adjustments to the KPIs and calculated attributes in the app’s Knowledge Model. Validating KPIs for the object-centric Payment Term Checker app explains the process.

  12. If you want to add custom values for the investigation status (besides the supplied values Open, In Progress, Resolved, and Rejected), configure the augmented attributes to add these. Configuring augmented attributes for the object-centric Payment Term Checker app has instructions to do this.

  13. If you want to customize the app’s views to change their look, fit your business process, or include custom items, edit them in Studio. Editing views for the object-centric Payment Term Checker app explains the process. You’ll need Analyst permissions for Studio and the views to modify them. If you make any changes to view components that involve the calculated attributes from the Knowledge Model, we’ll automatically update the calculated attributes in the Knowledge Model.

  14. When you’re happy with your results, publish a version of the app. There's a Publish button at the top of all the screens in your Studio space.

Tip

After publishing the package, if you make any further changes to variables in the Settings view, make sure you set these in both Studio and Apps. Changing the settings in Studio after publishing doesn’t affect the values in Apps.