10,718
edits
(→Data) |
|||
Line 70: | Line 70: | ||
First subgroup enables the user to allow or prohibit the mobile users to hide entities or show/hide the “Delete Data” button. | First subgroup enables the user to allow or prohibit the mobile users to hide entities or show/hide the “Delete Data” button. | ||
* Client Customize: Allow the mobile user to hide entities in the App Setup section. This setting does not use the Lock checkbox. If you leave the Value checkbox ticked, users will be able to use the Data part of the Setup and enable/disable entities. If you clear the Value checkbox, users will not see the Data part anymore and will not be able to enable/disable entities. | * '''Client Customize''': Allow the mobile user to hide entities in the App Setup section. This setting does not use the Lock checkbox. If you leave the Value checkbox ticked, users will be able to use the Data part of the Setup and enable/disable entities. If you clear the Value checkbox, users will not see the Data part anymore and will not be able to enable/disable entities. | ||
* Hide Locked Settings: Whether locked config options in SetupForm should be disabled or hidden. | * '''Hide Locked Settings''': Whether locked config options in SetupForm should be disabled or hidden. | ||
* Allow User to Delete Data: Show/Hide the 'Delete Data' button in the App Setup section. | * '''Allow User to Delete Data''': Show/Hide the 'Delete Data' button in the App Setup section. | ||
User can set the maximum size of the attachments to be created, captured photos, quality of captured videos or allow/prohibit photo cropping in the second subgroup. | User can set the maximum size of the attachments to be created, captured photos, quality of captured videos or allow/prohibit photo cropping in the second subgroup. | ||
* Max Upload Attachment Size: The maximum size of attachment (notes, email attachment) in bytes that can be created in the App. | * '''Max Upload Attachment Size''': The maximum size of attachment (notes, email attachment) in bytes that can be created in the App. | ||
* Capture Photo Size: The default photo size for photos taken in the App. | * '''Capture Photo Size''': The default photo size for photos taken in the App. | ||
* Max Export Records: The maximum number of records to export (in the 'Export' command). -1 - no limit. | * '''Max Export Records''': The maximum number of records to export (in the 'Export' command). -1 - no limit. | ||
* Audio/Video recording quality: The recording quality for audio or video taken in the App. (Affects file size!) | * '''Audio/Video recording quality''': The recording quality for audio or video taken in the App. (Affects file size!) | ||
* Allow Photo Cropping: Whether to show the photo cropping step after a photo is taken. | * '''Allow Photo Cropping''': Whether to show the photo cropping step after a photo is taken. | ||
* Save Signature As PNG: Whether to store signature as vector SVG image or PNG. | * '''Save Signature As PNG''': Whether to store signature as vector SVG image or PNG. | ||
Third subgroup provides a possibility to allow/turn off the encryption or use Sql Like Optimization. | Third subgroup provides a possibility to allow/turn off the encryption or use Sql Like Optimization. | ||
* Use Database Encryption: Whether to encrypt the device database that stores the offline CRM data. This setting does not use the Lock checkbox, as this setting is not available on the Mobile CRM Setup. Local database is encrypted by default on the mobile devices. It can be disabled though. | * '''Use Database Encryption''': Whether to encrypt the device database that stores the offline CRM data. This setting does not use the Lock checkbox, as this setting is not available on the Mobile CRM Setup. Local database is encrypted by default on the mobile devices. It can be disabled though. | ||
* Use Sql Like Optimization: Using this (SQLite) optimization can increase the BeginsWith operator performance for large data sets. (E.g., speeds up incremental search.) | * '''Use Sql Like Optimization''': Using this (SQLite) optimization can increase the BeginsWith operator performance for large data sets. (E.g., speeds up incremental search.) | ||
Last group houses settings for using of the Entity and Attribute map and [[Duplicate detection]] | Last group houses settings for using of the Entity and Attribute map and [[Duplicate detection]] | ||
* Use Entity & Attribute Map: Whether to use the Entity and Attribute Mappings (configured in CRM) when creating a new record. If you have an automatic field mapping set up on the CRM server, this parameter will enable the same functionality in the Mobile CRM application. | * '''Use Entity & Attribute Map''': Whether to use the Entity and Attribute Mappings (configured in CRM) when creating a new record. If you have an automatic field mapping set up on the CRM server, this parameter will enable the same functionality in the Mobile CRM application. | ||
* Duplicate Detection: Whether to use [[duplicate detection]] when creating a new record. | * '''Duplicate Detection''': Whether to use [[duplicate detection]] when creating a new record. | ||
* Auto Save Product Detail: Whether to edit the sales product detail entity directly or to apply changes on save. | * '''Auto Save Product Detail''': Whether to edit the sales product detail entity directly or to apply changes on save. | ||
* Ignore Missing Process Flow | * '''Ignore Missing Process Flow''': Whether to show an error if the Business Process Flow is not found. | ||
== Synchronization == | == Synchronization == |