Considerations for Using Flows in the Field Service Mobile App

Downloading Flow Data

When the app loads a user’s schedule data, it also downloads global flows and any flows scoped to records in their schedule data. Pulling down on the screen to sync with Salesforce causes the app to reload flow metadata.

Flow Input Parameters

When an iOS or Android app launches a flow, it passes the following input parameters:

• Id—The ID of the record that the flow is launched from.
• UserId—The ID of the current user.
• ParentId—The record ID of the parent record that the flow is launched from. For example, if a flow is launched from a service appointment, the ParentId is the ID of the parent work order or work order line item.

Creating a Choice Option

If the user selects the choice value to use in a screen component, such as a radio button or multi-select picklist, the screen component is set to this value. If no choice value is configured, the screen component is set to the choice label.

Using Flows with Case Assignment Rules

Mobile flows with record updates trigger assignment rules if the request updates an entity that has assignment rules in the same transaction for a case or a lead. To bypass assignment rules, in Apex run Assignment Rules with DMLOptions, and set the header Sforce-Auto-Assign as False.

Flow Limitations in the Field Service Mobile App

• Compound fields, for example street addresses, can’t be used directly in mobile flows. To access this data, fields such as city and country that comprise the compound field must be used instead.
• Select formula functions and operators are available offline.
• Backslash \ characters, single quotes ( ' ), and multi-line strings aren’t supported in flow formula fields.
• CRM Core App screen flows aren’t supported in the Field Service mobile app. Only Field Service mobile flows are supported.
• Email alert actions aren’t supported in flows.
• Paused flows aren’t supported. If you left a flow in progress or exit the Field Service mobile app, you can’t resume the flow where you left off.
• Flows with many CRUD operations can take a long time to process. To speed up this process contact Salesforce Support to request that the draft queue is paused.
• Flows cannot have dependencies on Apex or record triggers.
• Flows with deep links can cause issues and are not recommended at this time.
• The wasSelected operator can’t be used in decisions.
• For eval() functions, the boolean values true and false are case-sensitive.
• Hardcoded ID values must be 18 digits long. 15-digit values aren’t supported.
• Fault connectors aren’t supported in flows.
• When uploading images in flows, the content document IDs parameter isn’t supported. Admins must create a flow confirmation screen to show which images were uploaded. Videos and other file types aren’t supported.
• Flows don’t support the following elements. Adding these elements to a flow causes it to display an error.
  • Lightning components (except for file upload)
  • Output parameters on file upload except for “Uploaded File Names”
  • Choice resources with Display Text Input enabled
  • Actions with output parameters
    

    Note Some flows that have actions with output parameters don’t cause an error immediately, but they’re still not supported.
• Flows don’t support the Section screen component.
• Flow picklists that include a default value aren't supported. If you choose a default value, it isn't shown as the default value in the picklist and isn't used in the mobile flow. To work around this issue, add a separate choice that is a constant equal to the value of the default value in the object’s screen picklist value.
• In flows, radio button fields that aren’t required allow the user to select from a list of values, including a --None-- option. --None-- is a null value that allows the field to be optional.
• Flow picklists use the values of the choice set from which the default value is assigned.
• Flow record variables require record fields to be accessed through their field API names. Use of field relationship names isn’t supported.
• Record field lookups are limited to one level of indentation. If more levels are required, use assignment elements.
• Flow text areas have a 2,000-character limit.
• Using semicolons when defining user choices in flow checkbox groups and multi-select picklists isn’t supported. If you use semicolons for user choices, the data doesn’t render accurately.
• Record choice sets don’t retain the value that is selected. A record choice set variable can’t be used to determine what selection was made. However, the component used to make the selection, such as a picklist, saves that value for later use.
• Custom Logic and the or operator within Get elements and the record choice set variable aren’t supported in the Field Service mobile app.
• When using a flow that has a subflow, returning to the main flow from the subflow using the Previous button discards entered data.
• Recently added records from the Field Service org don’t show in mobile flows when using Flow Record Choice Set or the Get element to query from these records. To resolve this issue, log out and then back into the mobile app.
• Flows installed on the Field Service mobile app using a managed package result in an error. We recommend using an unmanaged package instead. This error only occurs on the mobile app.
• HTML text isn’t supported in Flow builder.
• Mobile flows support only these global values:
  • $Flow.CurrentDateTime
  • $Flow.CurrentDate
  • $GlobalConstant.EmptyString
• Flows on desktop and mobile don’t support picklist default values that are derived from an object’s picklist values.
• If a default value is assigned in the picklist component of the flow, then the values are populated from the default picklist field value and not the picklist choice set assigned to it.
• Running a flow as another user isn’t supported.
• Only the following assignment operations for collections are supported:
  • Add
  • Equal
  • Equals Count
• Picklist values are expanded if there are five or fewer values or if the picklist is the only component on that particular flow screen. Otherwise, values are displayed as a dropdown list.
• When a Record Choice Set is used as a data list for a single item picklist in a flow, the screen doesn’t display correctly. To work around this behavior, add additional items to the picklist.
• In mobile flow filtering, the user sees a related list instead of a picklist if these conditions are met:
  • The flow value store always has a specified parent ID (the parameter with ID passed in), unless the parent ID from the value store is nulled.
  • The user creates a screen step in the flow builder with a single field, and that field uses a single dynamic choice as choice reference. Additionally, the dynamic choice isn’t a picklist and contains the parent record ID as a filter.
  • The parent record identified by the parent ID has a dynamic choice type configured as a related list.
• Flows can have up to nine conditions in a decision element.
• Record Choice Sets created using the AttachedContentDocument objects on a Work Order or other supported object don't work in the mobile app. The mobile app doesn't support showing a related list for files within a flow.
• When using the NOW() formula in fields, create a separate formula resource that resolves to NOW(), and use that resource in the validation field. Doing so ensures the latest timestamp is used on the flow launch.
• Flows retain variable values after they’re entered. Clicking the Back button in a flow doesn’t clear the value.
• In Field Service mobile app flows that use the Create Record element, the ID populates with the app’s cache ID. This cache ID isn’t the newly created record’s ID. To access the cache ID in a flow on the app, you must turn on the option "Use separate resources, and literal values" in the Create Record element.
• Chaining of formulas in the same flow step isn’t supported.
• Collection Choice Sets aren’t supported in flows.
• Changing the name of or hiding navigation buttons in flows isn’t supported in the Field Service mobile app.
• When a mobile flow contains an image, the BeforeInsert trigger in Apex can cause an error.
• To remove access to custom objects, log out and then back into the mobile app.
• Conditional visibility isn’t supported, with the exception of Data Capture.
• The In and Not In operators in flows aren’t supported in the Field Service mobile app.
• Dependent picklists are supported in mobile flows but aren’t supported on the desktop site.
• Get elements in a flow are cached locally. Pull to refresh to get new data for Get records. This limitation doesn't apply to users with LDS enabled.
• Rich text in flows doesn’t show color in the Field Service mobile app.
• A custom flow for login must be set up when the Session Activation Required permission is enabled for Field Service mobile users. Without a custom flow for login, mobile users lose access to the Service Resource object and can’t log in to the mobile app.
• Flows that modify the Service Report Language field on the Work Order object don’t work offline.
• New records created using a flow in the Field Service mobile app don’t have the auto-number field data type’s value populated. The field isn’t populated, because the number is generated by the server during record creation and isn’t available locally on the app.
• Flow Builder on web allows users to assign empty values for record fields and are treated as null. However, on mobile, any fields in the assignment block with empty values are ignored, and no empty values are specified.
• You can’t update the chatter feed on a new record from a flow when LDS is enabled.
• Each Create, Update, or Delete action in a Field Service Mobile Flow runs as a separate transaction, meaning each action is processed individually. This behavior differs from the desktop experience, where multiple record changes can be grouped into a single transaction.

Available Formula Functions and Operators

Note Formula functions are case-sensitive. Make sure to use the formatting listed. For more details, see Formula and Operator Functions