Save and Validate a Data Draft

Save retains authoring work without replacing the current governed revision. The governed revision records approved intent. The draft records proposed changes. Compilation checks authored inputs and derives target-specific rules and validation findings. It does not publish those rules.

Before You Begin

Complete these prerequisites before saving the draft:

• Use your author account with edit capability and applicable owner/editor access.
• Configure the Data policy.

Save Proposed Work

To save the proposed policy work, follow these steps:

1. Review the title, classifications, principals, and protection permissions.
2. Select Save Draft. Policy compiles the current inputs before saving.
3. Inspect the returned notice. A successful Save returns you to the Library.
4. Reopen the policy in Policy Library.
5. Confirm the saved scope and draft status.

Record the policy identifier for later review and support. A successful Save can retain compiler findings or incomplete semantic work. It does not prove submission readiness, approval, or target delivery. Repeated saves retain snapshots within the same proposed revision. A snapshot records saved content and its validation evidence at that point. The latest snapshot is the draft head. Another Save advances that head, not the governed revision.

Inspect Findings

To review the saved validation findings, follow these steps:

1. Inspect outstanding exceptions and validation feedback for the saved draft.
2. Correct missing permissions, invalid scope, or unsupported selections.
3. Save the corrected work.
4. Reopen the saved draft to confirm the correction.

Do not assume that an unavailable or stale validation count means zero findings. Submission and approval revalidate current dependencies. Only explicitly reviewable conflicts permit acknowledgement with reasoning. Hard failures require correction. Acknowledgement cannot bypass them.

An authorized reviewer can refresh the exact saved head through GET /policies/{policy_id}/validation in the application programming interface (API) reference. That operation requires policy:review. An author without that capability must not use it as a diagnostic shortcut.

Recover Without Losing Intent

If Save fails, retain your edits and read the reported finding. For a connection or directory error, ask the administrator of the named integration to restore access before retrying Save. If you changed the form during compilation, save again using the latest edits.

If Policy reports that the draft changed, reload it and compare its content with your unsaved edits. In an API client, obtain a new Draft-ETag only after that comparison. For an uncertain response, inspect the Library before creating another policy. If the saved result remains unclear, preserve the policy identifier and support reference. Send those details to your Policy administrator instead of repeatedly selecting Save or creating another policy.

Next, submit the saved draft. For artificial intelligence (AI) preview, use AI preview and Save.