Process Hub · Use processes and complete work
How process drafts and submissions work
Know when work has been saved and when it has entered the business workflow.
On this page
Before you start
- Open the process record you intend to change. Each process defines its own draft, editing and lifecycle rules.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Read the record status. Draft capture, Submitted, Editable and Read only describe different conditions; a page being open is not proof that your changes are saved.
- Use Save draft to preserve unfinished permitted work. Wait for success and keep the record identifier so you can reopen the same draft.

Save draft keeps unfinished work. Complete required answers before starting final submission. - Use Submit for the final record action. A multi-page Next button moves between pages; it does not submit the whole record.
- For a form section with Submit batch, read its description: completing a section/batch can advance it while the outer form still needs Save draft or Submit.

Review the complete record. Back to edit returns to the form; Confirm submit performs final submission. - For a previously submitted record, Save changes is available only if the process/state and your access allow editing. Review approvals or lifecycle actions separately.
- On Android, a local saved/queued change must still synchronise to the server. Check Sync before assuming a supervisor can see it.
What you should see
You know whether your work is unfinished, saved locally, saved on the server, submitted or awaiting a further workflow action.
If something goes wrong
You cannot save a draft
Drafts may be disabled for that process or current operation. Complete the required flow or ask the process owner.
An approval did not start
Confirm the record was actually submitted and synchronised, then ask the manager to check the active automation release.