Dialogue Workflow Examples
Review draft. This source page has not completed website editorial and release-specific verification.
These examples use Dialogue-owned semantics. A generic Check selects an external provider configuration with ResolutionProfileId; the mechanics are not fields on the Dialogue asset. An optional Editor provider may help browse and describe profile IDs, while the base Editor always permits stable ID authoring without one.
1. Basic exchange
Section titled “1. Basic exchange”Connect Start to a localized Line, then to a Choice. Give each option a stable identity and route it to a follow-up Line or End.
2. Participant-aware Skill Check
Section titled “2. Participant-aware Skill Check”Create a Check node with a stable profile ID such as Combat.Intimidation.Standard, set ValueSourceKey to Skill, author the exact Skill ID and participant role, then choose comparison, target, and outcomes. Dialogue’s neutral Skill query service obtains the value from an optional registered provider. The external provider interprets the profile.
3. Numeric semantic input
Section titled “3. Numeric semantic input”Set ValueSourceKey to a project-defined semantic key, author BaseValue and ordered scalar inputs, then select a comparison and target. Do not put an asset path or implementation strategy in the Dialogue Definition.
4. Retry behavior
Section titled “4. Retry behavior”Choose a Dialogue-owned retry policy on the generic Check node. For ConditionReset, select the owning reset condition. Dialogue tracks attempt identity and retry state and preserves it in snapshots.
5. Random branch
Section titled “5. Random branch”Author ordered branch identities and integer weights. The registered provider selects a candidate. If no provider is registered, the branch returns ProviderUnavailable and routes to no candidate.
6. Weighted Dialogue Set
Section titled “6. Weighted Dialogue Set”Author eligible Dialogue Set entries with stable identities and weights. The provider selects one entry. Dialogue owns candidate ordering and the selected Set’s conversation start semantics.
7. Provider unavailable
Section titled “7. Provider unavailable”Run an ordinary Line and Choice conversation with no resolution provider to confirm those features work independently. When traversal reaches a generic Check or weighted selection, expect ProviderUnavailable. No authored Check failure route is taken.
8. Interchange
Section titled “8. Interchange”Export the Definition as typed schemaVersion 3 JSON. The generic Check fields include profile ID, semantic value source, comparison/target, optional Skill identity/role, scalar inputs, outcomes, and retry policy. Obsolete schema versions are rejected.