Plan Your Performance Priming Rollout Strategy
Follow these guidelines to ensure a smooth Performance Priming launch.
Required Editions
| Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience |
| The Field Service core features, managed package, and mobile app are available in Enterprise, Unlimited, and Developer Editions. |
| To access the Field Service mobile app, users need the Field Service Mobile user license. |
Performance Priming automatically generates briefcases using Service Appointment list views. Ensure that the filters for these list views are consistent across your sandbox and production environments.
When you update org configurations or roll out any new Field Service mobile features, you may need to log out mobile workers. Logging out mobile workers clears cached data, which requires a full download the next time the app is used. If all mobile workers log out and re-prime at the same time, this can place heavy load on your servers and impact performance. To avoid these issues, follow these best practices.
- Stagger logouts: Don’t log out all mobile workers at once. Instead, log them out in small groups, for example, by region, shift, or team.
- Roll out configuration changes gradually: Apply updates to a limited group first. Verify performance before extending the changes to more users.
- Stagger feature rollouts: When enabling new functionality, including priming improvements, release to subsets of mobile workers over time.
- Monitor and adjust: After each group, check performance, sync times, and error rates. Use these metrics to inform and plan following waves of the rollout.
- Communicate with mobile workers: Let mobile workers know when to expect a logout and re-login. Provide details on timing, expected behavior, and troubleshooting steps.
Did this article solve your issue?
Let us know so we can improve!
