Provided we have done the DML for the Parent prior to assignment to Child, we can then insert the Children in succession without the need to query for the newly created Parent Record Id to use in our Child SObject assignment. In Screen Flows we can create an Assignment for a new Parent record, and then reference that SObject Variable Id in the assignment of Children to that Parent.This necessitates more liberal use of branching in FSL Mobile Flows in order to compensate. The most glaring omission that will cause us difficultly is the lack of the IF() logical operator.Formulas are heavily used in Screen Flows for setting default values, populating variables, validating entries, governing branching logic and similar approaches.As a result, it is required to Activate and test from a mobile device before finalizing FSL Mobile Flows. The Debug works for FSL Mobile flows, but the results do not emulate running the flow from the Mobile App itself.to test flows during build and prior to deployment or activation.
The ‘Debug’ mode for Screen Flows is a critical feature in tracking steps, variables, etc.
What we will build over the next few posts….Īn FSL Mobile Flow for placing a Product Request!Ĭomparison of Screen Flow vs. Field Service Mobile Flows offer a flexible tool to surface business logic within the app, but these Flow types are significantly different than what we are used to with web-based Flows! Not to worry as we will walk through some of the differences and illustrate a few ways to account for them.
This post is part of a series focusing on building and providing an enterprise-scale service solution using the default FSL Mobile application.
This is a powerful and extensible out of the box application that enables our field organization to perform activities from an iOS or Android device. The FSL Mobile Application is a Salesforce app used in the Field Service Lightning product.