We're using Field Service with Data Capture forms (DDC flow). When a form is submitted, it closes the Work Order and the related Service Appointment.
Requirement
- A technician starts a form in the field and pauses it, leaving it partially complete.
- A back-office analyst has desktop access only. They need to open that paused form with every value the technician already entered, finish it, and submit it from desktop. Submitting should trigger the same Work Order and Service Appointment closure.
Problem
- The mobile flow supports pause/resume.
- The desktop DDC flow has no pause/resume. Launching it starts a brand-new run with blank values, so the analyst can't see the technician's partial data.
Questions
- Is there a supported way to resume a paused Data Capture session from desktop, or to load the technician's saved values into the desktop flow?
- Where is the paused form's data stored (which object or records), and can a flow read it to prefill the desktop run?
1. There is no native cross-platform feature to resume a mobile-paused Data Capture session directly from the desktop. This limitation exists because mobile pause states live locally within the Field Service mobile app architecture, whereas desktop flows initialize an entirely new interview context. Additionally, the behavior changes based on how the form is launched. Data Capture forms initiated via mobile Quick Actions do not generate a standard Form record and have stricter baseline limitations regarding pause/resume states compared to forms managed directly from the Forms tab.
2. Because paused flow states and variable values reside strictly within internal Flow Interview variables and device cache structures rather than queryable custom backend objects, they are hidden from the desktop environment.
To successfully enable a cross-device handoff, you must configure an intermediate persistence mechanism. We recommend writing partial inputs mid-flow to a custom staging object or utilizing custom fields on the parent Work Order or Service Appointment records. This architecture ensures that when a user launches the corresponding desktop flow, it can query those persisted database values and safely prefill the fields to resume the worker's session.
