Supported on all tiers:
The ProntoForms mobile app (iOS, Android, and Windows 10) can receive a “request” or “call” from another app on the same device (the source app). An inbound App‑to‑App request directs the ProntoForms app to launch in the foreground and complete an action. For example, the source app can direct the ProntoForms app to
open a new form and prepopulate it with data from the source app
open a list of forms in the user’s Inbox, or
search for previously submitted forms.
The source app can also specify “x‑callback” parameters. These parameters tell the ProntoForms app what to do when a user submits or discards a form, or when there’s an error. For example, after a user sends a form, ProntoForms can bring the source (calling) app back to the foreground and send the submitted form data to the source app.
Different source apps vary in their ability to use the data that ProntoForms provides in a callback.
Your source app must be configured to handle the callbacks and any data returned from ProntoForms. You might need to check with your own experts to set this up for your specific app.
We recommend that you configure a custom App‑to‑App allow list to manage the apps that can receive data from ProntoForms.
App‑to‑App callbacks are supported on the Advanced and Enterprise tiers only.
If you want the mobile device user to stay in the ProntoForms app, you don’t need to specify a callback parameter.
The combination of requests and callbacks enables offline communication between the source and ProntoForms apps, which is critical for managing step-by-step workflows such as checklists.
Tip:Organizations that use a work order management system can combine the offline functionality of inbound App‑to‑App communication with the online functionality of a ProntoForms cloud-based Data Destination. A Data Destination is typically used to send detailed data to the back-office system of the source app. Data Destinations enable full access to the data submitted from the ProntoForms app, including photos.