Operation Plan
Operation plan (execution plan) configuration allows you to specify the order of steps in the consolidation process, enabling fine-tuning of the MDM internal workflow for optimal performance.
The best way to alter the plan is to download one from the Admin Center (see MDM Admin Center Extras) and adjust the order of steps.
If the plan does not match the dependencies, MDM engine will reject the plan (but not fail) and use the default operation plan.
<?xml version="1.0" ?>
<executionPlanConfig>
<executionPlans>
<plan taskId="MasterDataConsolidation">
<steps>
<step id="Cleanse(Party)" />
<!-- more steps -->
<step id="Match(Party)" />
</steps>
</plan>
</executionPlans>
</executionPlanConfig>The plan element includes a taskId attribute, which uniquely identifies the operation plan.
The steps element contains multiple step definitions that represent a specific operation within the plan, identified by its id attribute.
| If the operation plan does not meet the constraints, the MDM engine ignores invalid input, logging warnings only in system logs. The same handling applies to situations where new entities or operations are introduced into the plan. |
To learn how to optimize performace, see Performance Tuning, section Operation plan optimization.
Was this page useful?