Task guide

Understand autosave, validation, and conditional wizard steps

Read save states, resolve validation, and understand why wizard sections vary between documents.

5 to 10 minutesFor Customers who edit or troubleshoot a CREBuilder documentBeginnerLast verified September 9, 2026

Outcome

You will leave each section with confirmed saved data and distinguish a hidden conditional section from a loading or permission problem.

Navigation path

Documents > Open document > Document Wizard

Access

Save and validation behavior applies to permitted document editors. Sections remain conditional on the document setup.

On this page

What you will accomplish

Property Data editor state used to verify autosave and required-field validation.
Watch the save state, resolve validation messages, and confirm that conditional steps reflect the document setup.

Goals

  • Recognize save states
  • Correct validation at its source
  • Explain why a section is present or absent

Safe navigation after editing

Treat the visible save state as the signal to continue.

  • Edit one fieldResolve validation
  • Resolve validationWait for Saved
  • Wait for SavedOpen next section

Before you start

Data, sources, and access to prepare

  • Access to the document
  • A stable network connection

Prepare these details

  • Note the document package, property type, template, and single or multi-property structure
  • Copy irreplaceable draft text before troubleshooting a persistent save error
  • Read the exact validation or save message

Complete the task

  1. 1

    Make one controlled change

    Current wizard section

    Edit one field or content block.

    Expected result: The section shows an unsaved or saving state.

    If this does not happen: Reload the section before editing if the existing data did not finish loading.

  2. 2

    Resolve one validation message

    Current wizard section

    Correct the field named by the message.

    Expected result: That validation message clears.

    If this does not happen: Check the field format and unit rather than repeatedly submitting the same value.

  3. 3

    Trigger the supported save

    Current wizard section

    Select Save when a Save action is present.

    Expected result: The save state changes to saving.

    If this does not happen: Keep the page open if the action is disabled while another request completes.

  4. 4

    Wait for confirmation

    Wizard header or section

    Wait for the Saved state.

    Expected result: The interface confirms that the current change completed.

    If this does not happen: If an error appears, preserve the input and retry once after checking the connection.

  5. 5

    Open the next section

    Wizard navigation

    Select Continue or an available section in Document Sections or the Sections drawer.

    Expected result: The wizard waits for pending saves before opening the destination.

    If this does not happen: If a save fails, the current section retains the input and shows Retry save. Retry before navigating again.

Save and section-state reference

Narrative drafts and many field edits save automatically. Dialogs, uploads and map creation keep their labelled save or confirmation actions. Continue, Back, Sections navigation and Save & Exit wait for pending wizard saves. A failed save keeps the input available and offers Retry save; it does not mean the change reached the server. Keep the page open until recovery succeeds.

Save and section-state reference
StateMeaningSafe response
Unsaved changesLocal edits have not completed savingStay on the section
SavingA request is in progressWait without repeating the action
SavedThe latest submitted change completedContinue and verify later
ErrorThe change was not confirmedKeep the input and retry after reading the error
Section absentThe setup may not include that sectionConfirm package, property type, scope, and template

Verify before you finish

  • Every edited section reached Saved
  • No visible validation remains
  • The section set matches the document setup
  • The edited values persist after revisiting the section

Troubleshooting and next steps

The save stays in progress.

Likely cause: A request or network response has not completed.

  1. Wait without clicking Save repeatedly.
  2. Preserve the entered content before refreshing if the state does not resolve.
A wizard step is missing.

Likely cause: The package, property type, financial scope, template, or multi-property mode may not use it.

  1. Compare the document setup with the expected workflow.
  2. Do not create substitute data in an unrelated section.

Final verification

  • Current wizard section: That validation message clears.
  • Current wizard section: The save state changes to saving.
  • Wizard header or section: The interface confirms that the current change completed.
  • Wizard navigation: The wizard waits for pending saves before opening the destination.
  • No blocking warning, failed status, or unresolved validation message remains in the completed workflow.

Was this guide helpful?