During our current FLS Mobile rollout, we have built many FLS Mobile screenflows that we are calling a number of different ways, including Deep Linking with formula fields, Global Actions, Record Actions, etc. They have saved us from going full LWC on a number of different requirements.
Now Data Capture forms has arrived, but I can't understand where it fits in? Unless I am missing something, the form has to be either manually added to each work order, or you need to create a flow to add it to all or a subset of work orders... what's the point? If we have to built a flow anways, wouldn't it be easier just to go with a screen flow?
Does anyone have specific examples where they found it made sense to do a Data Capture Form over a Flow? Thanks
@Bruce Stewart - Data Capture still has many of the same limitations as when I originally posted. The improvement is you can at least call the DCF from an Action now, but from the forms tab, you can't commit the changes without losing the form entry. Auto Capture only stores the record locally (on the device) until committed, so users cannot iterate over the form the way the would with a traditional Flow or LWC. We have used Voice to Form and it works fine, but the limitations of DCF are still there. Employee Agent will be Voice-to-Vocie soon, so that's the direction we are headed, full control over the logic. Thanks!
