Looking for information about ProntoForms features and functionality? Visit our Product Documentation Portal.
Tip:To improve efficiency and provide an optimal user experience, we recommend that you include all three x‑callback parameters in your requests.
- Opens the specified app or URL when the ProntoForms user saves or sends a form
, or when they transfer a ProntoForms Teamwork-enabled form.
- By default, when a ProntoForms user action triggers an x-success callback, ProntoForms returns the following data:
serverDataRecordID—the form’s unique ID on the ProntoForms server (if available).
clientDataRecordID—the form’s unique ID on the ProntoForms client.
pfStatus—the form’s current status on the device, as described in the following table.
Status Description Saved A ProntoForms mobile app user opened a form from the Forms box or Inbox, and then saved it. Outbox A submitted form is still processing on the user’s device and has not yet been uploaded to the server. This can happen when a device is offline, for example. Sent A submitted form was uploaded to the server.
Any custom callback parameters defined for the form.
- Opens the specified app or URL when the ProntoForms app can’t complete the requested action and generates an error.
- Opens the specified app or URL when the ProntoForms user cancels an action, such as discarding any changes made to the form.
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.