Other Configurations
This section provides pointers for optimum configuration of other options.
SFM Mobile Permissions
• Associate all the View Record and Standalone Create transactions with the Default Group profile.
• Then associate only the required View Record and Standalone Create transactions with each group profile used by mobile users. The above steps ensure that size of configuration data downloaded to mobile is minimized. This is because View and Create SFM transactions not associated with any group profile are downloaded for all mobile users.
• Associate all the Checklist transactions which are needed with each group profile specifically. Only the SFM Checklist transactions which are associated to the group profile are downloaded for the mobile users.
SFM Transactions
• Identify SFM transactions of types Source To Target, Standalone Edit, and Output Documents which are not required for mobile users.
• Adjust the mobile user profile permissions to remove object permission for either source or target objects where possible, for SFM transactions which are not required for mobile users.
• If this is not possible, identify lookup fields in the header page layout of such SFM transactions and remove access to one of these lookup field objects.
The above steps ensure that unused SFM transactions are not downloaded to mobile apps.
SFM Wizards and SFM Searches
• Associate all the wizards and searches with the Default Group profile.
• Then associate only the required wizards and searches with each group profile used by mobile users.
The above steps ensure that size of configuration data downloaded to mobile is minimized. This is because wizards and searches not associated with any group profile are downloaded for all mobile users.
Ensure that mobile user has access to all the objects and fields configured in the SFM searches available for the user.
Salesforce Configurations
• Define a custom permission set as a clone of ServiceMax Standard permission set and ensure the following:
◦ Permissions are granted on all the fields of all the relevant configuration objects listed in Access and Permissions section.
◦ Permissions are granted on all the Apex classes starting with the prefix SVMXC.COMM_ and SVMXC.INTF_.
• Add the above permission set to all mobile user accounts.
• Similarly, for each SFM transaction or a group of related SFM transactions, create permission sets reflecting all the required object and field permissions. Name the permission sets to indicate the SFM transaction(s) covered.
• Associate these permission sets with the mobile user accounts, to avoid / resolve permission-related issues.