Synchronization steps: Difference between revisions

Jump to navigation Jump to search
Line 111: Line 111:
=== Device configuration (remote [[device control]]) ===
=== Device configuration (remote [[device control]]) ===


This step only applies for deployments with Microsoft Dynamics.
The app sends device description to the CRM server, including the following parameters:
* SystemUserId
* Device ID, name, operating system, version of the mobile CRM app
* Device state (Normal | Wiped | Locked)


The app fetches <code>resco_mobiledevice</code> record that describes this device.
{{Note|App users can see their device ID in [[Resco_Mobile_CRM#About|About]] form, in the log file.|Tip}}


{{Note|The unique device ID can be seen in AboutForm log|Tip}}
This information is stored on the CRM server (Dynamics or Resco CRM server), in the entity resco_mobiledevice (Dynamics) or mobiledevice (Resco). Installations with Salesforce store this information in Resco CRM server.


The app receives information whether an administrator requested that the device is locked or wiped, forced full synchronization, or applied new security rules.
When a device registers at the server during its first synchronization, a new record is created. Each device has exactly one such record.


The app then sends device description to the server, including the following parameters:
So what happens in the app during synchronization:
* SystemUserId
# App downloads its resco_mobiledevice record from the server.
* Device ID, name, OS, MCRM version
# App performs the necessary management actions (for example lock device) or replaces the [[security policy]]. (Administrator can plan these actions using Woodford's [[Device control]] function. Technically, Woodford updates the resco_mobiledevice record for that device.)
* Device state (Normal | Wiped | Locked)
# App updates the record on the server.


=== Download mobile project from CRM server ===
=== Download mobile project from CRM server ===

Navigation menu