09 - Testing and saving

Info: This article is work in progress and subject to change.

A panel configuration moves through three operational states: edit while you are working on it, saved while end users can use it, and previous saved when an earlier configuration has been replaced but is kept for rollback. This article covers each state, the transitions between them, and the habits that keep the panel reliable for users while you iterate on it.

The Workflow Assistant Configurator does not have a draft state. Every change you make and save is part of the live edit; only the publish step makes it visible to users.

Note: The Configurator does not auto-save. The header shows a Saving… indicator while a save is in flight and a saved-state indicator when you are clean to navigate away. Always wait for the saved state before switching configurations or closing the tab.

Testing

The single highest-leverage habit in panel design: verify every change as a real test user before clicking Publish. The Configurator’s editor canvas is a structural preview; it does not run conditions, it does not simulate selections, and it does not represent what the user actually sees.

The end-to-end test loop:

Step 1. In the Configurator, save your changes. Confirm the saved-state indicator is clean.

Step 2. Switch to a second browser window where you are signed in to Assets as a test user — a non-admin user with the Required role.

Step 3. Refresh the panel (or re-open the asset to refresh).

Step 4. Verify the change you made:

• Does the new field appear?
• Does the visibility checklist hide the field for the kinds you intended?
• Does the disable condition fire for the assets you expect?
• Does the Notification appear with the right message?

Step 5. If anything is wrong, return to the Configurator, fix it, save, and repeat.

Step 6. Once the change behaves correctly under test, click Publish.

Tip: Saved but unpublished changes are not visible to end users. You can leave a configuration in a half-built state across days or weeks of work without users seeing partial changes — only the publish step pushes anything live. Use this freedom to test thoroughly.

Revisions

• 8 May 2026: First publication of the manual