Supported on all tiers:
As a form progresses through a workflow, it moves from one location (“box” or “tab”) on the ProntoForms app to another. For example, a user can open a form from the Forms box, add information, and then save it to Drafts.
Different identifiers apply at different stages in a workflow. When you build an App‑to‑App request, you must use valid combinations of identifier and location.
The following table describes the location-identifier combinations at various stages in a form’s workflow.
|Form stage||Location on the ProntoForms app||Identifiers to use in an App‑to‑App request||Description|
|Saved and deployed by a form designer||Forms||formID|
Identifies the form. In an App‑to‑App request, this is the most recently deployed version of the form.
Identifies the form and version of the form.
Identifies the form based on the ID assigned by the ProntoForms server.
|Dispatched, opened, and saved|
|Sent for edit|
|Sent for edit, opened, and saved|
|Opened for edit from the Sent box, and saved|
|Opened from the Forms box and saved as a draft||Drafts||clientDataRecordID|
Identifies the saved form by the ID assigned by the ProntoForms app.
Tip:The only way to get the clientDataRecordID is to send an App‑to‑App request that includes an
The search action searches the text of the submitted form name only.
Note:“Incomplete” applies only to teams on the Enterprise tier with ProntoForms Teamwork-enabled forms.