Creating Knowledge Models
As a Knowledge Model (KM) is a Studio package asset, you must be created either when a Studio package is created or added to an existing package. Both options allow you to either create a base model or extend an existing KM, with further details explained below.
To understand how Studio assets are structured, see: Workflow and content structure.
Knowledge Model types
When creating a KM, there are two types available to you:
Base: These are created using the business entities in your Data Model, populating the business entities automatically for you. Base KMs are independent from other KMs by default, however can be extended or used as a dependency.
Extension: You can extend KM from other packages by adding their origin package as a dependency. Extending KMs allow you to customize and add further business entities while reusing the core content, useful for managing region or account specific packages and other use cases.
With both KM types, you can then create additional entities or edit existing entities.
You can create a KM when you're creating a Studio package with either the View or Analysis initial content option selected. This creates a draft package with a KM that includes a number of entities auto generated from the Data Model associated with that package.
To create a Studio package from your Studio space:
Click Create Package.
Configure your package using the following fields:
Package name: Internal reference for this package.
Description: Optional added information, allowing other team members to read more information about this package.
Initial content: Select View or Analysis.
Data Model: Select the Data Model to use for this package.
Package key: Edit or copy the package key if you need to give other applications access to this package.
Language: Select which language this package should use as its default language.
Click Create.
The package is created and a KM asset is available. This KM is named after the Data Model selected when creating it, so in this example is it based on a Purchase to Pay Data Model.
Click into the Knowledge Model to view, edit, and create entities.
You can create a KM within an existing package, with no limit to the number that can exist within that package:
Click New asset - Knowledge Model.
Configure your KM using the following fields:
Name: An internal reference for this KM.
Key: The unique key used by other assets to reference this KM.
Data Model variable (optional): The variable that references the data you want to use in this KM. This variable can be updated or edited once the KM is created by using the Data Model drop down:
Knowledge Model type: Select between base or extend an existing KM. See: Knowledge Model types.
Click Create.
The KM is created and added to the package.
In addition to using the New asset - Knowledge Model steps outlined in the section above, you can also extend an existing Knowledge Model in a package by clicking Settings - Extend.
 |
This opens the Create Knowledge Model view and automatically lists the package containing the KM you're extending as a dependency.
You can then click Add Dependencies to select other Studio packages within your Celonis Platform team (depending on the permissions you hold for those assets).
 |
As a KM exists within a Studio package, you must publish the package. Studio gives you the ability to publish and control the version of packages and assets available to users through apps. This version control allow you to thoroughly test new features and configurations before using them productively.
For more information, see: Publishing and version control.
 |