Blueprint Developer Manual / Version 2406.0
Table Of ContentsThis action extends the AutoMergeTranslationAction and allows to configure a merge strategy. See Javadoc of AutoMergeSyncAction for details.
mergeStrategyVariable
| |
| Required | no |
| Description | The name of the variable into which the merge strategy bean name is stored. The bean name refers to a bean in the Spring application context that is an implementation of ThreeWayMerge. |
Table 5.36. Attributes of AutoMergeSyncAction
<AggregationVariable name="derivedContents" type="Resource"/> <AggregationVariable name="masterContentObjects" type="Resource"/> <AggregationVariable name="autoMergeConflicts" type="Resource"/> <Variable name="performer" type="User"/> <Variable name="mergeStrategy" type="String"/> <AutomatedTask name="Synchronize"> ... <Action class="com.coremedia.translate.workflow.synchronization.AutoMergeSyncAction" autoMergePredicateFactoryName="allMergeablePropertiesPredicateFactory" derivedContentsVariable="derivedContents" masterContentObjectsVariable="masterContentObjects" resultVariable="autoMergeConflicts" performerVariable="performer" escalateOnConflict="true" mergeStrategyVariable="mergeStrategy"/> </AutomatedTask>
Example 5.43. Usage of AutoMergeSyncAction
A custom merge strategy for a synchronization workflow can be configured by either by implementing the interface ThreeWayMerge or SyncThreeWayMerge and adding the bean to the Spring application context. The interface SyncThreeWayMerge allows control about whether a property needs to be merged or updated.
The bean name can be passed to the synchronization workflow via the variable mergeStrategy. How to add a custom merge strategy to the studio client is decribed in Section 9.26.10, “Synchronization Workflow Specifics” in Studio Developer Manual.
