Map Your Processes From SAP Signavio to LeanIX
The tab Basic Configuration consists of two sections. This page will describe how you can leverage the first section, called SAP Signavio Processes, to map your processes from SAP Signavio into your LeanIX workspace. It is important to understand that this part of the integration is one-directional and only works from SAP Signavio to LeanIX.
Information
When synchronizing processes, SAP Signavio should always be the system of record and LeanIX the consumer.
1. Sync Mode
A sync mode for integration configuration can be defined in three ways, depending on the specific requirements of preserving/ deleting the items from the target system.
Additive Sync: This Sync Mode only creates and updates items and never deletes anything. This is the safest Sync Mode, but it can lead to duplicate data if not used carefully.
Conservative Sync: This sync mode only deletes items created in the target system and are no longer linked to any source object. This Sync Mode preserves manually created items and items that are linked to sources controlled by other integrations. Items that were created by a different integration (e.g., Collibra) or another Signavio configuration will be preserved as well as part of this sync.
Overwrite Sync: This Sync Mode deletes any items that are not linked to a source object or that are linked to a source object that no longer exists. This Sync Mode is the most likely to lead to data loss, but it is also the most likely to ensure that your data is consistent with the source system.
Sync Mode Availability When Multiple Signavio Configurations Are Active
When using multiple Signavio configurations in a single workspace, Overwrite Sync mode cannot be used. In workspaces where multiple Signavio configurations are active, the Overwrite Sync mode will be unavailable to avoid erroneous deletion of fact sheets.
Sync Mode behavior:
Direction | Additive Sync | Conservative Sync | Overwrite Sync |
---|---|---|---|
Foreign → LeanIX (LeanIX is the target) | No deletion will happen | Every Fact Sheet will be deleted that has an externalId of the running configuration, but the corresponding item on the source is missing, AND no further externalId is specified on the Fact Sheet. | Every Fact Sheet will be deleted that has NO externalId of the running configuration or this externalId links an object that does not exist. |
LeanIX → Foreign (Foreign is the target) | No deletion will happen | Every Foreign item from the target will be deleted if no Fact Sheet is found that is linked to this item, considering the configuration externalId. This will happen if a previously linked FactSheet is archived or the item in the foreign system is manually created. | Every foreign item from the target will be deleted that has no valid link to a FactSheet when considering the configuration externalId. |
Alternative Name Computation When Using Multiple Signavio Configurations
When you're synchronizing data from a foreign system to LeanIX, it's common that you want to use the original name of the foreign object as LeanIX's Fact Sheet name. However, this can potentially lead to conflicts, especially when one Fact Sheet is linked against two source systems.
To avoid such conflicts, integration has a mechanism to create an additional Fact Sheet with a different yet deterministic name. This alternative name computation ensures uniqueness while maintaining a clear reference to the original source system.
The alternative name is built according to the following rule: <configured name in mapping> (<name of configuration>)
- "Configured name in mapping”: for Signavio, it is the “title”
- "Name of Configuration": This is the unique name each configuration has. It's used to differentiate between different configurations.
By using this rule, we ensure that each Fact Sheet has a unique name, thus avoiding any conflicts. At the same time, the alternative name gives clear information about its origin, making it easy to trace back to the source system if needed.
2. Use Interval
If you enable the Use interval option, then the integration will automatically run every 3 hours between 6 AM and 6 PM CET/MEZ. This setting must be checked for the top-down hierarchy synchronization (see step 6). In case you want to customize the scheduling, click on the button ...
after enabling the option. It will allow you to choose any hour of the day to start the integration.
3. Fact Sheet Type
Choose the Fact Sheet Type to which the information should be synced. The process is the most logical Fact Sheet Type to choose.
If you have a LeanIX Meta Model v4, then you have the possibility to synchronize the processes to the “Business Context” Fact Sheet. The “Process” subtype is the most logical subtype to choose to sync the processes. In order to synchronize to a specific subtype, please follow the steps:
- Navigate to “Edit Field Mappings” by clicking the button
**...**
next to Edit Directories on the right. - Add a mapping of type “Static Text”.
- Choose “Subtype” in the LeanIX column.
- Choose a value to map as a subtype (e.g., Process) in the SAP Signavio column.
- Click OK and save the config.
4. Active
You can activate/deactivate the mapping of the processes within the configuration. This is especially helpful if you want to test different settings on other parts of the configuration without synchronizing the processes.
5. Short Description
Use this field to briefly describe which processes you map from SAP Signavio to LeanIX. You may leave this field empty.
6. Process Hierarchy
The integration is able to map the hierarchy of your processes within SAP Signavio into a relationship between your LeanIX Fact Sheets.
Relationships Created in the Hierarchy
Parent-child relationships are created for the hierarchies detected between Processes in SAP Signavio EXCEPT when we detect (in LeanIX) a double parent situation, then we choose a different relation in the Fact Sheets, which is RelToRequires.
You can choose between three different options: The hierarchy can be synchronized bottom-up, top-down, or not be synced.
Do Not Synchronize Hierarchy
In this mode, the integration will synchronize based on a given list of SAP Signavio directories. To configure this list, click on the button Edit Directories . A new dialog will open that allows you to select a LeanIX Parent Fact Sheet and a list of SAP Signavio Directories.
The Fact Sheet you choose as the LeanIX parent will be the parent for all processes discovered in the given list of SAP Signavio directories. If no SAP Signavio directory is selected, the public root directory is used.
Synchronize Hierarchy Bottom-Up
In this mode, the integration searches for defined processes (based on the LeanIX Fact Sheet) in the list of configured SAP Signavio Directories (and their child directories) and synchronizes all processes from the bottom to the highest level processes.
In this mode also, you need to provide a LeanIX Parent Fact Sheet and a list of SAP Signavio Directories using the Edit Directories dialog.
Synchronize Hierarchy Top-Down
In this mode, the integration will start at the specified root node and synchronize all processes walking down the hierarchy. The option Use interval (see step 2) is mandatory for this configuration. To configure the root node, click on the button Edit Hierarchy to open a new dialog.
In the dialog, you can choose a process that will be used as the root node of your hierarchy. You may also choose a list of processes that will be ignored during the synchronization.
7. Published
This mode allows you to decide whether all SAP Signavio processes should be synchronized or only the published ones.
8. Edit Directories / Edit Hierarchy
These buttons are used to configure the process hierarchy, as explained in step 6.
9. Edit Field Mappings
When clicking the button ...
at the end of the row, a new dialog opens that allows you to configure the Field Mappings. These mappings define how SAP Signavio attributes are mapped onto LeanIX Fact Sheet fields.
Use the Documentation field on top to describe the intention of your field mappings for later reference.
After that, you may add multiple field mappings, each having a Mapping Type and a reference to LeanIX and SAP Signavio.
Default Mapping
In case no mappings are specified in the Edit Field Mappings Modal, the integration will synchronise the name and the description of an SAP Signavio Process into a Fact Sheet by default.
We offer three mapping types: Simple, Expression and Static Text.
Simple
As the name suggests, the Simple type should be rather self-explanatory and thus simple to use. In the list of references to the LeanIX Fact Sheet, you will find:
- Fields on the Fact Sheet, e.g., scalar fields (text, number...) but also single & multi-select fields
- Subscriptions and Subscription Roles
- Tags and Tag Groups
In the list of references to the SAP Signavio Process, you will find:
- Fields on the Process model, e.g., scalar fields (text, number...) but also single & multi-select fields
- Fields on any linked Dictionary Item
For single and multi-select fields, tags, and tag groups, use the Value Mapping option to specify which value on the LeanIX side is used for which value on the Signavio side.
Mapping Processes to Different Subtypes
In a single process hierarchy sync, you can map multiple processes from Signavio to different Fact Sheet Subtypes in LeanIX. In the field mapping modal, choose Subtype for LeanIX and choose Type for the Signavio.
Then, through value mapping, you can specify and map processes from Signavio to Fact Sheet Subtype Process and value chains to Fact Sheet Subtype Value Stream.
Expression
The Expression Mapping Type is Deprecated
The expression mapping type is deprecated as it is rather difficult to explain. Please refer to the Advanced Configuration for more details.
Static Text
This mapping type can be used to write a static text into a text field on the Fact Sheet. If you choose this type, the static text can be entered into the text field presented in the column SAP Signavio.
Updated about 2 months ago