For the Synchronization Workflow, a custom merge strategy can be added to the merge strategy chooser of the Start Synchronization Workflow Panel.

This customization requires a change for the Studio client and the Workflow Server. The change for Studio client is described in this section, for customization of the workflow-server refer to Section, “ AutoMergeSyncAction ” in Blueprint Developer Manual .

Adding a merge strategy for a synchronization workflow on the Studio client side is done via the AddMergeStrategyPlugin which is part of the package @coremedia/studio-client.main.control-room-editor-components.

import { workflowPlugins } from "@coremedia/studio-client.workflow-plugin-models";

workflowPlugins._.registerMergeStrategy("CustomSyncWorkflow", "newMergeStrategy");

In order to add localization for a new merge strategy you can utilize the WorkflowLocalizationRegistry of the package @coremedia/studio-client.workflow-plugin-models.

import CustomSyncWorkflow_properties from "./CustomSyncWorkflow_properties";
import { workflowLocalizationRegistry } from "@coremedia/studio-client.workflow-plugin-models";

workflowLocalizationRegistry._.addMergeStrategyLocalization(
  "CustomSyncWorkflow",
  "newMergeStrategy",
  {
    displayName: CustomSyncWorkflow_properties.newMergeStrategy_displayName,
    description: CustomSyncWorkflow_properties.newMergeStrategy_description
  });

Workflow Validation Settings

Just as for translation workflows, a preview of dependent contents is calculated when starting a synchronization workflow. As this may take a considerable amount of time to evaluate for huge changesets, limits can be configured within Spring configuration properties as well as within content settings.

Here, synchronization shares the same settings as for the translation workflow (both summarized as localization workflows). For available configuration options take a look at Section “Workflow Validation Settings”.