A Cluster is a system entity that virtually groups one or more records based on the Matching Rules defined for a given entity. Unlike standard relationships, the connection between records within a cluster exists on a virtual level – no physical link is created between them at this stage.
Clusters are used as part of the duplicate detection workflow. When duplicate search is enabled for an entity – within the master data, within the contributor data, or between master and contributor – the system automatically groups the detected duplicates into clusters to facilitate review and processing.
A correctly formed cluster contains one master record and one or more contributor records. Once the user consolidates a cluster item, a real relationship between the master and contributor records is established.
Creating and Deleting Clusters
Clusters are created automatically by a scheduled job based on the Matching Rules configured for the entity. Users cannot create clusters manually, nor can they add or remove cluster items manually.
Regardless of the cluster's current status, items may be added to or removed from it on each subsequent job run.
A cluster can only be deleted if it has no cluster items (i.e., its status is "Empty").
Cluster Fields

| Field | Description |
|---|---|
| Number | A unique auto-incremented identifier, assigned automatically by the system. Read-only. |
| Master Entity | The master entity this cluster belongs to. A cluster is always scoped to a single entity and may only contain records from that master entity and its corresponding contributor entity. |
| Golden Record | The primary master record to which contributor records will be linked upon consolidation. Only one Golden Record can be set per cluster. If the Golden Record is deleted, all contributor items are unlinked from it. |
| Status | A read-only, dynamically calculated field reflecting the current status of the cluster. Updated automatically on any change to cluster items. |
| Consolidation Method | How the cluster was consolidated. Read-only. See Consolidation Method and Execution Mode. |
| Execution Mode | Whether the consolidation was executed by a user or by the system. Read-only. See Consolidation Method and Execution Mode. |
| Contributor Item Count | The number of contributor records currently linked to the cluster. Read-only. |
| Master Item Count | The number of master records currently linked to the cluster. Read-only. |
The Status field of the Cluster can have the following values:
- Empty – the cluster has no cluster items.
- Review – the cluster has items, but is not yet fully consolidated.
- Consolidated – all contributor records of the cluster are linked to its golden record. Use the Execution Mode field to see whether the consolidation was done by a user or by the system.
- Invalid – the cluster contains more than one master record, or contains no contributor records.
Consolidation Method and Execution Mode
Each cluster stores how it was consolidated. Both values are set by the system on consolidation and cannot be changed manually.
Consolidation Method describes the principle used to build the Golden Record:
| Value | Description |
|---|---|
| Rule-based | The Golden Record is built by the Consolidation Script. Set by the Consolidate action, by automatic consolidation and by the Manual Consolidation View if all values are taken from the Consolidation Script. |
| Hybrid | A user selected the Golden Record values in the Manual Consolidation View and took some of them from the Consolidation Script and some from the cluster items. |
| Manual | A user selected all Golden Record values in the Manual Consolidation View from the cluster items. |
Execution Mode describes who executed the consolidation:
| Value | Description |
|---|---|
| Automatic | The consolidation was executed by the Create Clusters scheduled job. |
| Manual | The consolidation was executed by a user. |
Both fields are empty while the cluster has no Golden Record. Each subsequent consolidation of the cluster overwrites both values, e.g. a manually merged cluster becomes "Rule-based" after a user takes all values from the Consolidation Script in the Manual Consolidation View.
Automatic consolidation never processes clusters with the consolidation method "Manual" or "Hybrid", so the result of a manual merge is not changed by the Create Clusters job. If the job joins such a cluster with another one, the resulting cluster keeps the consolidation method "Manual" or "Hybrid", and new items in it stay unconsolidated until a user merges them in the Manual Consolidation View.
Confirming and consolidating a cluster item are different steps. Confirmation means the record belongs to the cluster, while consolidation links the record to the Golden Record. Consolidation also confirms the item. If the confirmation was done by the Create Clusters job, the item is marked as confirmed automatically.
Cluster Items
Cluster Items panel lists all master and contributor records that the system has linked to the current cluster based on the entity's Matching Rules. Each item displays the Entity Name, the linked Record, and its Matched Score.
Cluster items cannot be added or removed manually. If a Matched Record is deleted, the corresponding Cluster Item is not removed – instead, it is reassigned to another cluster (existing or newly created).
Every contributor record must belong to a cluster. If the system detects no duplicates for a given record, a cluster with a single item is created and that item is consolidated automatically.
Cluster items are created, populated, and automatically consolidated by the Create Clusters scheduled job. If matching rules change, or a record is created or updated causing a Matched Records pair to be added, removed, or have its Matched Score changed, the cluster is not updated immediately – changes take effect on the next job run.
Cluster View Modes
The Cluster entity supports three view modes, switchable via the buttons in the cluster detail view:
-
Standard View – displays all cluster fields along with two relation panels: Cluster Items and Rejected Cluster Items.
-
Comparison View – displays a comparison table with the fields and attributes defined in the Selection Layout of the corresponding entity.
-
Manual Consolidation View – displays all cluster items side by side with radio buttons for selecting field values from each record. Used to manually build or update the Golden Record by choosing specific values from contributor records. See Merge Cluster Items for details.

Field values that differ between records are highlighted with a vertical red line. The comparison table shows a maximum of 5 items at a time.
Each column in the comparison table includes a Matched Score row for the corresponding item. Field values in the table can be edited directly.
The Matched Score row in each column shows icons indicating the entity role and consolidation method:
![]()
- 1 – the record is a master entity record.
- 2 – the record is a contributor entity record.
- 3 – the item was confirmed automatically by the
Create Clustersjob.
The Golden Record is indicated by a horizontal gold line in the comparison table. A consolidated contributor record is indicated by a horizontal blue line.
To control which items are shown in the comparison table, open the Item tab in the left sidebar. It lists all items belonging to the cluster, grouped by entity. Use the eye icon next to each item to show or hide it in the table.
Items in the left sidebar are grouped by status within each entity section:
- Not Consolidated – items that are neither consolidated nor rejected, shown at the top of the section.
- Consolidated – a collapsible group listing consolidated items.
- Rejected – a collapsible group listing rejected items; collapsed by default.
Grouping is applied separately for Master and Contributor entities. Each item in the sidebar has an actions button (⋮) that provides item-level actions directly from the sidebar without opening the item's detail page.

Cluster Information in Record Detail View
When a record belongs to a cluster, a Cluster Information block is displayed in the right sidebar of the record's detail page. This block provides a quick overview of the associated cluster without navigating to the cluster itself.

The block includes the cluster status (e.g., Consolidated) and the date of last modification.
Below the cluster summary, two collapsible panels are displayed:
- Master Records – lists all master records linked to the cluster.
- Contributor Records – lists all contributor records linked to the cluster.
Record names within both panels are clickable links that open the respective record's detail page.
The status of each item is visually indicated by a colored horizontal line on the left side of the record name. Items confirmed automatically display an additional icon.
Merge Cluster Items
The Manual Consolidation View allows you to manually create or update the Golden Record within a cluster by selecting individual field values from contributor records via radio buttons. Values can also be taken from the Consolidation Script.

To execute the merge, click Consolidate. The action is available only for clusters with the status "Review" or "Consolidated".
All cluster items are shown in the Manual Consolidation View by default. To exclude an item from the merge, use the unset icon in the left sidebar. Only items that were removed from the merge interface are considered non-participating – all others are treated as participating in the merge.
Suggested Values
The first column of the Manual Consolidation View is Suggested Values. It shows the Golden Record as the Consolidation Script builds it from the unconsolidated items of the cluster. By default, all field values are taken from this column. Select the radio buttons of the cluster items for the fields whose values should be chosen manually. The radio button in the column header selects the script values for all fields again.
The values in the column cannot be edited. On execution, the script is rendered again, so the Golden Record gets its current result. Relations are not calculated by the script. They are taken from the cluster item selected in the header, or from the first cluster item if the Suggested Values column is selected in the header.
If the Consolidation Script is missing, fails or returns no values, an error is shown and the values in the column cannot be selected. The merge with values from this column is not executed in this case.
Behavior on execution:
- If no Golden Record exists, it is created; if one already exists, it is updated.
- Field values are taken from the contributor records based on the radio button selection in the Manual Consolidation View.
- Participating contributor records are not processed through the Consolidation Script – selected values are applied directly, except for the fields taken from the Suggested Values column.
- Participating cluster items are consolidated after the merge is executed.
- Contributor records that did not participate in the merge (i.e., removed from the merge interface) remain unchanged.
- If a field in the Golden Record is locked via a value lock, the lock is ignored – the selected value is applied regardless.
- The merge is executed on behalf of the current user – the Execute Consolidation As setting of the Consolidation is ignored. The user needs the permissions to create and edit the master record.
- Update Master Automatically is not triggered by the merge, so the selected values are not overwritten by the Consolidation Script.
- The cluster gets the consolidation method "Rule-based" if all fields are taken from the Suggested Values column, "Manual" if none of them, otherwise "Hybrid". The execution mode is "Manual".
Cluster Item Actions
The following actions are available for cluster items in both Standard and Comparison views:
-
Consolidate – creates a link between the contributor and master records. Two scenarios apply:
- If a master record already exists in the cluster, the contributor record is linked to it.
- If no master record exists yet, a new master record is created based on the selected contributor record and linked to it.
An already consolidated item cannot be consolidated again. Not available for clusters with the consolidation method "Manual" or "Hybrid" – use the Manual Consolidation View for them. The cluster gets the consolidation method "Rule-based" and the execution mode "Manual". Available as a mass action – can be executed for multiple cluster items at once, but only for items belonging to the same cluster. All selected items are consolidated together into one master record.
-
Reject – removes the cluster item from the current cluster and reassigns it to another cluster (existing or newly created). The rejected item remains visible in the
Rejected Cluster Itemspanel. If a consolidated master record is rejected, all consolidated contributor records in the cluster are automatically deconsolidated and the link between the master and contributor records is removed. If a consolidated contributor record is rejected, that record is deconsolidated. Available as a mass action – can be executed for multiple cluster items at once. -
Unreject – Available for items in the
Rejected Cluster Itemspanel. Returns the item to the cluster. If the item was previously consolidated, then rejected, and then returned to the cluster, it is not consolidated and must be consolidated again. -
Deconsolidate – unlinks the contributor record from the golden record of the cluster. The cluster item stays in the current cluster and can be consolidated again. If Update Master Automatically is enabled for the consolidation, the golden record is updated according to the Consolidation Script based on the remaining contributor records. For clusters with the consolidation method "Manual" or "Hybrid", the golden record is not updated. Available only for consolidated contributor records. At least one contributor record must stay consolidated, so the last consolidated item cannot be deconsolidated, and all consolidated items cannot be deconsolidated at once. Available as a mass action – can be executed for multiple cluster items at once, but only for items belonging to the same cluster.
-
Split – moves the selected cluster items to a new cluster. Consolidated items are deconsolidated first, as described for Deconsolidate. Unlike Reject, all selected items are guaranteed to end up together in the same new cluster, and no rejection is stored. Not available for the master record. Available as a mass action – can be executed for multiple cluster items at once, but only for items belonging to the same cluster.
-
Move – transfers the cluster item to an existing cluster selected by the user. A cluster picker dialog opens, filtered to clusters of the same master entity. If the item was consolidated, it is deconsolidated before the move. If the item is the Golden Record, the source cluster loses its Golden Record. The item cannot be moved to a cluster where it was previously rejected. Both the source and target clusters record the move in their activity streams.
-
Delete Deletes the corresponding record and its cluster item.
Consolidating Cluster Items
When a cluster item (master or contributor record) is consolidated, the system creates a Golden Record for the cluster if one does not yet exist. If a Golden Record is already set, consolidating additional items links the corresponding contributor records to that master record. The linked contributor records become visible in the relevant relation panel on the master record's detail page.
Consolidation Script
During consolidation, all cluster items are processed through the Consolidation Script defined in the Consolidation configuration for the corresponding master entity.
This script describes the logic by which the master record is created or updated based on the contributor record – specifying which fields should be copied, under what conditions, and whether any field transformations should be applied.
Automatic Consolidation
Cluster items can be consolidated manually by the user or automatically by the Create Clusters scheduled job.
To enable automatic consolidation, check the Consolidate Automatically checkbox in the Consolidation record of the corresponding master entity. When enabled, the Minimum Matching Score field becomes required and defines the threshold for automatic consolidation.
A cluster item is consolidated automatically if its Matched Score is greater than or equal to the Minimum Matching Score. If the score falls below this threshold, the item will not be consolidated automatically, even if the setting is enabled for the entity.
Clusters with the consolidation method "Manual" or "Hybrid" are skipped by automatic consolidation. Automatic consolidation sets the consolidation method "Rule-based" and the execution mode "Automatic".
Items confirmed automatically are marked with a dedicated icon in the cluster.

The Matched Score is copied from the corresponding Matched Record to the cluster item. If the matching chain is A → B with a score of 80 and B → C with a score of 60, the scores assigned to the cluster items will be: A – 80, B – 80, C – 60.
Automatic Master Update
When Update Master Automatically is enabled in the Consolidation configuration, any update to a contributor record will automatically trigger an update of the corresponding master record according to the Consolidation Script – without requiring a manual re-consolidation.
If automatic field locking on manual modification is enabled, updates from contributor records will not overwrite fields in the master record that have been modified manually.
Automatic Removal of Invalid Masters
When Delete Invalid Masters Automatically is enabled in the Consolidation configuration, the system automatically removes invalid master records from clusters that already have a Golden Record set.
A cluster is considered to have invalid masters when it contains more than one master record – a state reflected by the "Invalid" cluster status. In this situation, all master records in the cluster except the designated Golden Record are considered invalid. With this option enabled, those excess master records are deleted automatically during the Create Clusters job run.
This setting is useful to automatically clean up master data in scenarios where duplicate detection identifies master records that should not coexist independently and should instead be consolidated under the cluster's Golden Record.
Purging Clusters
Purging permanently deletes one or more clusters along with all their ClusterItems and RejectedClusterItems. Unlike the standard delete action, which requires a cluster to have the status "Empty", purge removes a cluster regardless of its status.
This is a hard delete. Purged clusters and their items cannot be recovered.
Purge All
The Purge All button is available in the top-left area of the Cluster list view. It purges every cluster in the system regardless of any active filters or selection. A confirmation dialog is shown before execution.
Purge selected
To purge a specific set of clusters, select them in the list view, open the mass action menu, and choose Purge. A confirmation dialog is shown before execution.
Sync vs. async execution
| Clusters affected | Behaviour |
|---|---|
| Up to 200 | Executed immediately; the UI waits for completion |
| More than 200 | Dispatched as background jobs; progress can be monitored in the Job Manager |
Activity Stream
Each Cluster has an activity stream that records all significant events on its items. The following events are tracked:
| Event | Description |
|---|---|
| Linked | A record was added to the cluster |
| Unlinked | A record was removed from the cluster |
| Rejected | A Cluster Item was rejected |
| Reincluded | A previously rejected item was returned to the cluster |
| Moved | An item was moved out of the cluster |
| Deconsolidated | A contributor record was unlinked from the golden record |
| Consolidated | A Cluster Item was consolidated |
| Golden Record | A record was set as the Golden Record |
| Deleted | The underlying record was deleted |