10,730
edits
Important: Deprecating old WebView — Publish failed error
Synchronization steps: Difference between revisions
Jump to navigation
Jump to search
→Device configuration (remote device control)
| Line 111: | Line 111: | ||
=== Device configuration (remote [[device control]]) === | === Device configuration (remote [[device control]]) === | ||
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) | |||
{{Note|App users can see their device ID in [[Resco_Mobile_CRM#About|About]] form, in the log file.|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. | |||
When a device registers at the server during its first synchronization, a new record is created. Each device has exactly one such record. | |||
So what happens in the app during synchronization: | |||
# App downloads its resco_mobiledevice record from the server. | |||
# 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.) | |||
# App updates the record on the server. | |||
=== Download mobile project from CRM server === | === Download mobile project from CRM server === | ||