Select a Flow Cache Policy for the Field Service Mobile App
Flow cache policies determine when and how data is fetched and used within flows for the Field Service mobile app. You can select flow cache policies that optimize your flows in low-connectivity areas.
Required Editions
What Are Flow Cache Policies?
Salesforce Field Service customers often encounter varying data dependencies in their flows, from online-only scenarios to offline support. Flow cache policies determine when and how data is fetched and used within a flow. Defining your flow cache policy lets you optimize flow performance and ensure that flows run efficiently even under bad network conditions.
Flow cache policies determine when and how data is fetched and used within a flow. By setting a suitable cache policy, you can control whether the flow should always use the latest data from the network, rely on cached data, or a combination of the two. This can significantly affect the performance and reliability of flows, especially in environments with unstable network connectivity.
Benefits
- Improved performance: By using cached data, flows can run quicker and more efficiently, especially in bad network conditions.
- Flexibility: Admins can tailor the cache policy to meet the specific needs of their organization, ensuring optimal performance and reliability.
- Offline support: The Cache Only policy enables flows to run smoothly even when the app is offline, enhancing the user experience in field service scenarios.
Selecting Flow Cache Policies
The default cache policy is Network If Available. The flow first attempts to fetch data from the network. If the network is unavailable, the flow uses the cache.
You can also select the Cache Only policy. To do so, contact Salesforce Support to turn on the feature. With the Cache Only policy, the flow always pulls data from the cache, without attempting to fetch data from the network. Cache Only is suitable for scenarios where the latest data is not required and performance is a higher priority. This policy can significantly improve flow performance in bad network conditions.
Considerations
- If you choose to apply the Cache Only policy, make sure that your data is updated and refreshed through other mechanisms such as briefcase, standard offline priming, list views, or Lightning web components. If the data is not refreshed, the flow can’t access the required data.
- If updated records aren’t loading in a new Cache Only flow on your mobile device, pull to refresh and make sure you have access to the most up-to-date data.
- Online-dependent flows sometimes need to wait for the second emit to reload the flow step, causing disruptions to the flow.
Select Your Policy
Set your cache policy in Flow Builder to optimize flows in the Field Service mobile app and control when and how data is fetched and used within a flow.
| User Permissions Needed | |
|---|---|
| To set cache policies: | Enable Cache Policy Selection Feature for Field Service Mobile Flows |
- From Setup in the Quick Find box, enter Process Automation, and then select Flows.
- Select the flow you want to configure to enter Flow Builder.
- Select Advanced Settings.
- Under Cache Policy, choose the desired cache policy from these options in the dropdown menu.
- Network If Available (Default): The flow first attempts to fetch data from the network. If the network is unavailable, the flow uses the cache.
- Cache Only: The flow always pulls data from the cache only, without attempting to fetch data from the network.
- Save your changes.
Test the flow in a sandbox environment to make sure it meets your requirements and works as expected.
- Enhance Productivity with the Cache First Policy
The Cache First policy in the Field Service mobile app improves data load speed and performance for record details screens and related lists. This update replaces the previous online preferred policy, making the app faster and more accurate if you’re using Lightning Data Service.
