37.1 Draft and Published States

AIUNIFY Chat Agents have a Draft/Live publication state. The Agent workspace displays the current state and provides the normal user-facing publishing action.

A newly created or unpublished Agent displays Draft. A published Agent displays Live or Published depending on the screen.

37.2 Why Publishing Matters

Publishing creates a versioned snapshot of the Agent and associates that snapshot with the Agent's published version.

This provides a defined publication point rather than treating every edit as an uncontrolled live deployment.

37.3 Publishing an Agent

1. Open the Agent workspace.
2. Confirm that Knowledge has been added and indexed.
3. Test realistic questions in the Playground.
4. Review the Agent's settings and customization.
5. Select Publish.
6. Wait for the operation to complete.

Once published, the setup workflow can mark the Agent ready for website installation.

37.4 Re-Publishing

If the Agent is already published, the workspace action changes to Re-publish.

Use Re-publish after you have made and tested changes that should become the next published Agent snapshot.

37.5 Publication Versions

The deployed application creates an immutable Agent-version record when the Agent is published. The Agent stores a reference to the currently published version.

This version model provides the technical basis for rollback to an earlier published snapshot.

37.6 Rollback Capability

The deployed application includes a protected Agent rollback operation. Rollback requires a specific prior Agent version and restores the snapshot associated with that version.

The operation validates that the selected version belongs to the same Agent before applying it.

37.7 Current Workspace UI Availability

In the deployed source inspected for this manual, the normal Agent workspace visibly provides Publish and Re-publish, but the current workspace page does not render a version-history or Roll back control.

Therefore, normal users should not attempt to construct a rollback request manually. Use rollback only when a supported version-history/Roll back action is actually presented through the AIUNIFY Chat interface for your deployment.

37.8 If a Roll Back Action Is Available

When a future or deployment-specific interface exposes version history, select only a prior version belonging to the same Agent and confirm the rollback deliberately.

After rollback, review and test the Agent before assuming the restored state is correct for current visitor traffic.

37.9 Re-Publish vs. Rollback

• Re-publish creates a new published snapshot from the Agent's current configuration.
• Rollback restores a prior published snapshot.

37.10 Publication Best Practices

• Test before publishing.
• Review Knowledge health before launch.
• Use Re-publish intentionally after meaningful changes.
• Do not manually call protected rollback routes.
• If rollback becomes available in the interface, verify the selected version carefully.