Overview
In the scope of Enterprise Architecture, Ardoq is used as the source of truth for applications that exist within an organization. Instead of setting up applications and IT systems in both Ardoq and CPM, and then managing both systems separately, you can instead export applications from Ardoq to CPM on a scheduled basis.
This way as new applications enter Ardoq, they can be effortlessly brought to CPM, where they can be attached to processes and activities. Finally, using the CPM Importer, you can bring back updated data from CPM back into Ardoq to complete the full cycle.
Connecting Ardoq to CPM
Configuring CPM to Accept Applications
Before we can export to CPM, we need to configure a custom attribute in CPM to store Ardoq OIDs to maintain synchronization. This configuration will expose a custom parameter on the CPM API that Ardoq will use to store custom IDs.
In CPM, switch to editor mode by clicking the pencil icon in the top-right corner.
Click the gear icon that appeared in the top-right corner.
Under the Configure tab, click on Extended configuration
Create a new attribute called
ardoqIDof the type Add singleline text attributeSelect the
ardoqIDattribute and turn on the following options in the sidepanel:Set Available in REST API to on
Set Language independent to on
Set Activate to on
Set Valid for types to Systems → Applications
Set Group to Details
Click Apply changes
Creating a Connection to CPM in Ardoq
When creating your API token in CPM, ensure that the token has author permissions.
From the main menu in Ardoq, select Home > Import and integration then navigate to the Celonis Process Management Exporter. On the next page, select the Connections tab, then select Create new connection and fill in the required details:
Connection name
The sub-domain at symbioweb.com
Symbio API Token
Collection
Storage
Preferred language (1033 for English)
Once completed, the connection will automatically appear in the CPM exporter connection field.
Exporting Applications
Selecting Components to Export
The CPM exporter only exports from one workspace at a time. Each export can bring over any component types within that workspace, to be configured separately.
By default, Ardoq pre-defines the following field to export to CPM based on existing component properties:
Component name
Ardoq OID
Description
You can also add the following optional fields to the exported applications:
System complexity
System Production From
System Production Until
System Pilot From
System Pilot Until
System Planned From
System Planned Until
System Phase Out From
System Phase Out Until
System Switched Off From
Finally, the applications need to have a defined parent field, which corresponds to the building block elements attached to the System Architecture in CPM. Applications can be exported to existing building blocks or you can create a new building block in Ardoq.
Once your configuration is done, you'll see a preview of the components to be created or updated. If the export finishes successfully, you'll be able to schedule the export on a daily or weekly basis to keep your applications up to date.
The exported applications will be created in the In process state and will only be visible in editor mode until they are published.