Configuration
There are three core configuration aspects applicable to any mobile app:
• Meta data: Definitions, processes, and rules that determine how data must be controlled, displayed, and processed
• Data sets: Transactional data necessary to enable the mobile users to carry out their core business activities
• Synchronization options: When meta and transactional data should be synchronized and how data integrity should be maintained
The following sections describe these configuration aspects as they apply to ServiceMax mobile apps. Of these, data sets and synchronization options are configured using Mobile Configuration screen. Meta data configuration is through other ServiceMax configuration screens and Salesforce configurations.
Meta Data
• Labels and messages in the user’s language
• Object and field definitions and permissions, including record types, picklists, and dependencies
• SFM transactions, wizards, and searches, along with strings translated into user’s language
• ServiceMax configuration setting values
Data Sets
• Event window configuration
• Download Criteria configuration
• Advanced Download Criteria configuration
Synchronization Options
• Sync frequencies for configuration, event, and data sync
• Sync conflict handling options
• Data purging options
Download vs. Advanced Download Criteria
Of the mobile configuration options available, Download and Advanced Download Criteria are similar in nature, but have a key difference because of their purpose. This section describes that difference in the context of examples.
With Download Criteria configuration, the only conditions that can be specified are based on the object’s attributes. For example, one can define Download Criteria to download all the Installed Products in a particular city, in Installed state, and so on. But, it is not possible to qualify Installed Products based on the attributes of another object such as Work Order.
But most common requirement is to be able to download records related to another primary record which is downloaded. Example of a primary record is a Work Order record. With Download Criteria configuration, it is not possible to specify download of all the Contacts associated with the Work Order’s Account, or all the Installed Products in the Work Order’s Location.
Advanced Download Criteria enables such configuration, for primary records associated with events.
Advanced Download Criteria also enables configuration of related record for a primary record, where the relationship is one-level instead of two-levels as described above. For example, it is possible to configure download of Account, Contact, and Installed Product referred in Work Orders. This configuration is similar to ‘Related Objects’ configuration applicable to legacy Offline Client. This too is applicable for primary records associated with events. The same configuration is to be used to configure downloading of Attachments.
See Also: