pattern-library checked
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.
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. |
Evidence Role
This source is treated as pattern-library evidence. Use it to validate the decision rules above, not as a visual style reference.
Publisher: SAP Fiori Design System. Last checked: .