Communicating Data Model Changes
Learn about communicating with data model changes.
The data model is either defined on a central server or a test system. After applying the changes to the active data model, these changes are available on the server: you need to communicate changes to the data model to branch offices and/or other Aurea CRM products. The entire data model is transferred and overwrites the current data model on the target station. For more information on merging data models, see Merging Data Models.
Communicating changes to branch offices
The data model is saved as a format. It is communicated to branch offices (irrespective of the settings in your communication format) whenever the data model is updated.
When communicating, the system checks whether the data model on the main office and target station are identical. If not, the data model is updated on the target station before importing any other data, see Input in the Aurea CRM win Administrator Guide.
During manual communication, the changes to the data model are input first. You are then prompted to restart the communication process. You need to close and reopen the Communication module and restart the input process.
This step is carried out automatically during automatic communication.
Transferring Changes via CRM.cockpit
For information on communicating data model changes using CRM.cockpit, refer to the CRM.cockpit documentation.
Transferring Changes to other Aurea CRM Products
Apply the changes to the CRM.designer database using CRM.bulkloader, see Data Model, CRM Processes, Roles and Catalogs in the Aurea CRM web Administrator Guide. To immediately transfer changes to the data model to other Aurea CRM products, the corresponding application pool needs to be stopped and restarted.
For information on transferring changes to formats to Aurea CRM web, see Station Configuration.