Installing the object-centric Open Purchase Order Management app
The object-centric version of the Open Purchase Order Management app works with objects and events created for object-centric process mining. Before you set up the object-centric version of the Open Purchase Order Management app, you’ll need to enable and configure the Procurement process, load the object-centric data model with your data, and validate the perspective_celonis_Procurement perspective. See Prerequisites for the object-centric Open Purchase Order Management app.
You can download the Open Purchase Order Management app from the Celonis Marketplace. When you link the Open Purchase Order Management app to the perspective_celonis_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 Order Management app:
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.
Select the Open Purchase Order Management (object-centric) app to see its information page.
Select Get it now to install the app. There's no Process Connector to download for the object-centric app, because it uses the data that's already in the OCPM Data Pool.
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.
Click Assign perspective when the app prompts you. This takes you to the Variables tab in the Settings view.
Select the Assign Data Model button, then search or browse for the supplied perspective_celonis_Procurement perspective and click to select it. Click Save to set the Data Model variable.
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 Open Purchase Order Management app explains how.
The Open Purchase Order Management app needs publishing before configuration to get the profile views, tasks and augmented attributes working correctly. Select the Publish Package 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. The Permissions settings are available from the package’s context menu (the three vertical dots by the package name). 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.
Open the Open Purchase Order Management 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.
Use the Settings view to set up the runtime variables for the app. See Configuring settings for the object-centric Open Purchase Order Management app.
Tip
Because the Open Purchase Order Management app needs to be published right away, you’ll need to change the settings in these views in Apps as well as in Studio. Changing the settings in Studio after publishing doesn’t affect the values in Apps.
Check that the business logic used by the KPIs (key performance indicators) in the app’s Knowledge Model is correct for your business. Validating KPIs for the object-centric Open Purchase Order Management app explains how, and lists the most important KPIs to check. You’ll need Analyst permissions for Studio and the Knowledge Model to modify any of the KPIs and their calculations.
If you want to add custom values for status and priorities, configure the augmented attributes to add these. Configuring augmented attributes for the object-centric Open Purchase Order Management app has instructions to do this.
Configure the tasks and actions for the app. Configuring tasks and actions for the object-centric Open Purchase Order Management app tells you how, and explains what needs configuring.
If you want to customize the app’s views to change their look, fit your business process, or include custom attributes or relationships that you added to the Celonis object types used in the perspective_celonis_Procurement perspective, edit them in Studio. Editing views for the object-centric Open Purchase Order Management app explains the process. You’ll need Analyst permissions for Studio and the views to modify them.
When you’re happy with your results, publish a version of the app. There's a Publish Package button at the top of all the screens in your Studio space.
Tip
After publishing the package, if you make any further changes to runtime 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.
When you publish the Open Purchase Order Management app for the first time, the augmented attributes will be created, and the smart sensors will be triggered, as well as the records of the tasks.