Runtime Fields and User Intents

STConversationRunner exposes two application-controlled inputs into declarative Conversation execution.

Runtime fields hold named values. They are useful for collected data, application state, dynamic prompt content, and other values referenced by the Conversation.

User intent is a separate application-supplied routing signal. A Conversation can evaluate that intent in its transition logic.

Keeping these concepts separate is useful: a field represents data/state, while user intent represents an application-directed transition input.

_ = conversation.setRuntimeField("CollectedName", value: "Antoine")
_ = conversation.setUserIntent("confirm")

The detailed syntax for referencing fields and declaring transitions belongs to the Conversation Configuration Reference.