SAP Fiori: Draft Handling
Documents drafts as interim versions of business entities, automatically saved in the background, used to preserve interrupted editing, prevent data loss, support validation and dynamic fields, lock editing, resume drafts in edit mode, and distinguish draft persistence from final active save.
What this source can teach
Use this source to compare a documented solution with the task and states in your own product.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Autosave form | Choose autosave form when background progress preservation is safer than relying only on a final Save button. | Editing a field marks that field or section pending without clearing the user's value. | SAP Fiori supports background draft saving, interrupted-edit recovery, validation, locking, resume editing, and final active save distinction. |
| Autosave recovery | Choose autosave recovery when a background save did not complete or cannot prove that the latest value is safe. | The recovery surface appears close to the affected form, section, editor, or submit action and remains until the risk is resolved. | SAP Fiori supports background draft persistence, interrupted-edit recovery, validation, locks, and active save distinction. |
| Draft state | Choose draft state when a recoverable unpublished version exists separately from a published, active, or previously saved version. | Opening a draft from a list lands in draft edit mode and preserves the unpublished values. | SAP Fiori supports active versus draft entities, resume or discard choices, draft deep links, draft filters, unavailable draft recovery, and locked editing status. |
Comparisons supported by this source
- Autosave form vs single-page form vs multi-step form vs inline edit
SAP Fiori documents background draft saving, resume editing, locking, validation, and distinction between drafts and final active save.
- Autosave recovery vs autosave form vs draft state vs retry
SAP Fiori documents background draft persistence, interrupted editing recovery, validation, locking, and active save distinction.
- Draft state vs autosave form vs inline edit vs complete complex form
SAP Fiori documents resume or discard dialogs, active and draft entities, deep-link behavior, draft filters, and editing status such as own draft and locked by another user.
Evidence Role
This source is treated as pattern-library evidence. Its value comes from the specific claims and setting described above.
Publisher: SAP Fiori Design System. Last checked: .