Merge in 3.0


How does the "Create/Update Object" work? When service center detects that the same object has differences in both OML, does the update simply overwrite the object, or is there some merge mechanism at the action level. For example, consider that both versions have been changed prior to the cloning, and that the importer OML invokes a new action "Action A", whereas the imported OML invokes a new action "Action B": Does the resulting OML include both actions, or just "Action B"?


Hello João,

When Service Studio detects that the same object was changed both in the local and foreign OML, merging that object overwrites the object in the local eSpace. Using your example, the merged OML would only include an invocation for "Action B".

Best regards,