Automerge
Description
Automerge creates the table _CEL_MERGED_ACTIVITIES by merging all available and 'mergeable' event logs into the default event log.
Automerge uses MERGE_EVENTLOG functionality to merge all mergeable tables in a tree-structured manner.
The default eventlog is the target eventlog. That is enhanced by the activities of all connected eventlogs. This means that cases that exist in the case table of the target eventlog will get more activities from other eventlogs that have a join relationship to this case. If a case does not exist in the case table of the target eventlog, it will not appear in _CEL_MERGED_ACTIVITIES. Even if an activity has a join partner in another activity table but those have no connection to the default activity table, these activities will not show in the table _CEL_MERGED_ACTIVITIES.
If automerge is enabled (or disabled), a full data load is required for the change to take effect.
If the case table of an activity table is connected to the rest of the data model (where the default activity table is configured) via the activity table, we ignore the activity table.
Result Columns
The automerge result table contains the three default event attribute columns which always have the names CASE_ID, ACTIVITY and TIMESTAMP. These contain the merged content of the default columns from the activity tables and replace the original column names. For example, if there is the activity table "O2C_ACTIVITIES"
with the activity column "ACTIVITY_EN"
, the merged result would be in "_CEL_MERGED_ACTIVITIES"."ACTIVITY"
. All other columns of the data model activity tables are also merged and added to the result table under their original name.
If activity tables have the same column name but different types, separate columns are added to the table _CEL_MERGED_ACTIVITIES. We assign them a name that is the concatenation of the column name and the column type.
Examples
[1] All columns from the three activity tables | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[2] The column ADDITION5 appears in table Table1_Activity and Table3_Activity with type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|