As the concept of creating copies of objects at the time of scoping comes into picture with v4.2, one may wonder whether how the changes made to copies of objects in the project RCM can be made to reflect to the corresponding objects in Core RCM. The copies of object are created so that a line can be drawn between the core RCM objects and project RCM objects and the objects in core RCM and project RCM can be handled independently. The whole process has been made so flexible that the objects in the project scope can now be retained even if the corresponding objects in the Entity Hierarchy are deleted.
Still, one can feel the requirement of syncing the objects in the project RCM with core RCM. Syncing can be done so as to reflect the changes made in the copy to the core.
Note: Syncing can be done only for the fields which are enabled by the administrator via the Project Settings.
Note: You will require permissions on the Core RCM and its sub-objects so as to sync the updates.
Note: The new records are displayed as Green text to visually differentiate them from other records.
Sync Inability Conditions and Permissions
You will not see the check boxes against the RCM sub-objects if they satisfy the following conditions and permissions:
Note: Hover the mouse cursor over the RCM sub-object with no check box to view the relevant condition.
Sync Exceptions
Known Issue: The following fields are not synced in the core RCM after performing the RCM Sync operation: