Skip to main content

Installing the object-centric Open Purchase Requisition Processing App

The object-centric version of the Open Purchase Requisition Processing app works with objects and events created for object-centric process mining. Before you set up the object-centric version of the Open Purchase Requisition Processing app, you’ll need to enable and configure the Procurement process, load the object-centric data model with your data, and validate the perspective_custom_Procurement.

You can download the Open Purchase Requisition Processing app from the Celonis Marketplace. When you link the Open Purchase Requisition Processing app to the perspective_custom_Procurement perspective, it uses the objects and events that you’ve already built from your source system data and stored in the OCPM Data Pool. You don’t have to create a new data connection.

Here’s how to install the Open Purchase Requisition Processing 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 versions. Only the object-centric Catalog 3.0 version is suitable for object-centric process mining.

  2. Select the Open Purchase Requisition Processing (object-centric) app to see its information page.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 Open Purchase Requisition app.

  3. 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.

  4. In the Studio overview, find the Open Purchase Requisition Processing app package in the space where you installed it, and click its tile to go to the app package.

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

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

  7. Set the Knowledge Model key for your local app installation, as the value of the Knowledge Model Key variable in the app’s Knowledge Model. Setting the Knowledge Model Key variable for the object-centric Shipped Not Invoiced app explains how.

    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 Open Purchase Requisition Processing app needs publishing before configuration, because publishing triggers the creation of the task table and initializes the augmented attributes (Status, Priority, Note). 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 Open Purchase Requisition Processing view 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 Setup and Validation and Value Assessment view and the Settings view to set up the runtime variables for the app. See Configuring settings for the object-centric App Name app.

  11. Work through the steps in the Setup and Validation view to change the default parameters from the Knowledge Model to align with how things are done in your organization. If anything is still not the way you want it, you can make further adjustments to the KPIs and calculated attributes directly in the app’s Knowledge Model. . Validating KPIs for the object-centric Shipped Not Invoiced app explains the process.

  12. If you want to add custom values for Status, Priority or Note fields, configure the augmented attributes to add these. Configuring augmented attributes for the object-centric Shipped Not Invoiced app has instructions to do this.

  13. Configure the tasks and actions for the app. Configuring tasks and actions for the object-centric Shipped Not Invoiced app tells you how, and explains what needs configuring.

  14. 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 Shipped Not Invoiced 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.

  15. 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 Setup and Validation view or 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

  16. When you publish the Open Purchase Requisition Processing app for the first time, it creates the table for tasks. At least one skill must be executed for the table to get created - you can use the Smart Sensor for this.