Available in: Axsy Mobile for Salesforce, Axsy Field Service, Axsy Public Sector, Axsy Retail Execution
The Axsy Mobile App includes support for Salesforce Screen Flows.
Figure 1 - Salesforce Flow designer within the Salesforce Web UI
NOTE: In order to access Screen Flows in the app, users need to add the Flow Action to the Salesforce Mobile and Lightning Experience Actions section of the page layout for an object.
NOTE: Other Flow types (e.g. Auto-launched Flows) are designed to run on the Salesforce Platform and are not supported on the Axsy Mobile App.
Object Permissions for Flows
The data that is synced to the app as part of initial sync is limited by the user's object and record permissions configured on the Salesforce Platform. Subsequently, for a Screen Flow to run successfully offline, a user needs to have the necessary permissions to access the data, objects and records required by that Flow. If the user has been given the sufficient permissions and the Axsy Config Tool has been configured to sync all required records for the Flow, the Screen Flow will run as expected in Offline Mode for that specific user.
Effectively, running a Flow on Axsy is architecturally equivalent to running the flow in User Context Mode on Salesforce.
New Flows and Newly Activated Flow Versions
When new Flows or new Flow versions are activated, they will only be available to a mobile app user after:
1a) A New Config Version is published with metadata generation enabled (see this article for reference); OR
1b) The user is configured to receive Draft Config Settings (see this article for reference) AND
2) The user logs out and back in to their mobile app.
Supported Flow Components
The following tables list the Axsy Mobile App's support for the various Flow Elements, Resources, Data Types and Screen Components. Please make note of any applicable Limitations later on in this article.
| Flow Element | Element Type | Supported? |
|---|---|---|
| Screen | Interaction | Supported |
| Action | Interaction | Limited - No support for Apex or LWC |
| Subflow | Interaction | Supported |
| Assignment | Logic | Supported |
| Decision | Logic | Supported |
| Pause | Logic | Not supported |
| Loop | Logic | Supported |
| Collection Sort | Logic | Supported |
| Collection Filter | Logic | Supported |
| Create Records | Data | Supported |
| Update Records | Data | Supported |
| Get Records | Data | Supported |
| Delete Records | Data | Supported |
| Resource Type | Supported? |
|---|---|
| Variable | Supported |
| Constant | Supported |
| Formula | Supported |
| Text Template | Supported |
| Stage | Not supported |
| Data Type | Supported? |
|---|---|
| Text | Supported |
| Record | Supported |
| Number | Supported |
| Currency | Supported |
| Boolean | Supported |
| Date | Supported |
| Date/Time | Supported |
| Picklist | Supported |
| Multi-Select Picklist | Supported |
| Apex-Defined | Not supported |
Screen Component | Supported? |
|---|---|
| Address | Coming Summer '24 |
| Checkbox | Supported |
| Checkbox Group | Supported |
| Currency | Supported |
| Choice Look Up | Not supported |
| Data Table | Supported |
| Date | Supported |
| Date & Time | Supported |
| Dependent Picklists | Supported |
| Display Image | Supported (See Limitations) |
| Supported | |
| File Upload | Supported |
| Long Text Area | Supported |
| Lookup | Supported |
| Multi-Select Picklist | Supported |
| Name | Coming Summer '24 |
| Number | Supported |
| Password | Not supported |
| Phone | Supported |
| Picklist | Supported |
| Radio Buttons | Supported |
| Slider | Supported |
| Text | Supported |
| Toggle | Supported |
| URL | Supported |
| Display Text | Supported (See Limitations) |
| Section | Supported |
Screen Element Conditionality | Supported? |
|---|---|
| Visibility | Supported |
| Validation | Supported |
| Record Fields | Supported |
Axsy Specific Function | Details |
|---|---|
| $Flow.InterviewGuid | Example usage: ISBLANK({!$Flow.InterviewGuid}) Returns TRUE if Flow is running in Axsy Mobile App, otherwise FALSE |
Limitations
The Axsy Mobile App has the same Flow limitations as the Salesforce Field Service Mobile App, outlined in this article: Considerations for Using Flows in the Field Service Mobile App. Additionally:
| Limitation | Details |
|---|---|
| Complex Conditions | Conditions such as FUNCTION 1 && (FUNCTION 2 || FUNCTION 3) are not currently supported. These will be supported in a future release. |
| Operators | The following operators are not currently supported.
These will be supported in a future release. |
| Functions | The following function is not currently supported.
This will be supported in a future release. |
| Display Image Screen Component | We do not pre-cache images referenced from the flows, so they will only be displayed if the flow is running online or has run online before. |
| Display Text | Rich text formatting will be supported in Axsy Summer '24. |
| Global Error Handling | Not currently supported. Will be supported in a future release. |
| Lightning Components | Limited to:
|
| Comparing Strings to Global Constant Boolean Values | No support for comparing record file types of Text or Picklist to global constant values:
Instead, these record field types can be compared to the String values 'true' and 'false'. For example, boolean Retail Visit KPIs store their Target and Actual values within Text fields, meaning these fields need to be compared against String values. |
| Flow Global Variables | Limited to:
|