What you will do
You will save a draft to Test, preview it on a representative product page, review its dependencies, publish the intended version, and verify the result in Production. The same release loop applies to agents, actions, capabilities, guides, brand, and the Resource Center, with the entity-specific controls described below.
Saving makes a change testable. It does not make the change live for customer traffic.
Knowledge content has a separate lifecycle: accepted ingestion and removals automatically
update the shared corpus, including content used by published experiences. Articles have no
individual Publish action. Publish an experience or capability when changing its knowledge
scope. See Knowledge delivery.
Publish states
A safe release loop
1
Save in Test
Finish the configuration and make sure required fields and placement rules are valid.
2
Review dependencies
Check capabilities, actions, knowledge, brand, Guidance, and referenced Resource Center
content. For Ask, include the Resource Center Agent’s capabilities and knowledge scope.
3
Exercise representative cases
Test success, confirmation, decline, unavailable dependencies, navigation, error, and stop
behavior.
4
Publish explicitly
Publish the intended entity and any selected dependencies. Publishing one entity must not be
assumed to publish every reference automatically.
5
Verify Production
Confirm the published version, intended page targeting, identity mode, and customer-owned
executor in the target environment.
Unpublish and archive
- Unpublish removes an entity from Production while its latest saved version remains available in Test.
- Archive removes the entity from Test. If the entity is still published, its Production version remains until a separate unpublish.
- Unarchive returns the saved entity to Test.
- Restore version makes a previous published snapshot the working version for review.