Installing the object-centric Unshipped Orders app
The object-centric version of the Unshipped Orders app works with objects and events created for object-centric process mining. Before you set up the object-centric version of the Unshipped Orders app, you’ll need to load the object-centric data model with your data and validate the perspective_celonis_OrderManagement perspective. See Prerequisites for the object-centric Unshipped Orders app.
You can download the Unshipped Orders app from the Celonis Marketplace. When you link the Unshipped Orders app to the perspective_celonis_OrderManagement 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 Unshipped Orders app:
Open the Celonis Marketplace from the Celonis navigation bar, and search for all or part of the app’s name.
Select the Unshipped Orders (object-centric) app to see its information page.
Select Get it now to install the app. There's no data 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.
In the Studio overview, find the Starter Kit package in the space where you installed it, and click its tile to go to the app package.
Click the Package Settings icon (the box) and select Variables.
Select the Assign Data Model button, then search or browse for the supplied perspective_celonis_OrderManagement perspective and click to select it. Click Save to set the Data Model variable.
The Unshipped Orders app needs publishing before configuration for the Status, Comment, and Tasks columns to work. 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. 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 Setup and Validation 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 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 Setup and Validation View and the Settings view to set up the variables for the app. See Configuring settings for the object-centric Unshipped Orders app.
Tip
Because the Unshipped Orders app needs to be published right away, you’ll need to change the settings in these views in Apps and Studio. Changing the settings in Studio after publishing doesn’t affect the values in Apps.
Check that the business logic used by the KPIs and calculated attributes in the app’s Knowledge Model is correct for your business. Start with the Setup and Validation view, which guides you through setup for key KPIs. Validating KPIs for the object-centric Unshipped Orders app explains how to check the calculated attributes in the Knowledge Model. You’ll need Analyst permissions for Studio and the Knowledge Model to modify any of the KPIs and calculated attributes.
If you want to add custom values for the status of deliveries (besides the supplied values “New”, “In Progress”, “Done” and “Rejected”), configure the augmented attributes to add these. Configuring augmented attributes for the object-centric Unshipped Orders app has instructions to do this.
Configure the tasks and actions for the app. Configuring tasks and actions for the object-centric Unshipped Orders 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, edit them in Studio. Editing views for the object-centric Unshipped Orders 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.
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.
When you publish the Unshipped Orders app for the first time, it creates tasks, creates the augmented attributes, and links the views with their profile views.