Amend Entity is supported only for English dialog task conversations. Scope: entity value replacement only (not partial modifications, deletions, or additions).
How It Works
- Amend Identification — The platform’s built-in NLP detects the user’s intent to amend.
- Amending Entities — Three flows based on utterance:
- User refers to entity name: prompted for new value. (If entity appears multiple times, the most recently populated one is amended.)
- User provides entity value: entity is updated. (If value matches multiple entities, user selects which to amend.)
- User refers to both entity name and value: entity is updated directly.
- Post-Amendment Behavior — Three options:
- Re-execute dialog from the amended node (evaluating its connections).
- Resume from the node where the amend was identified.
- Resume from a specified node.
Configuration
Amend behavior is set at two levels. Task-level settings override app-level.App Level
- Go to Natural Language > NLU Config > Amend Entity.
- Enable Allow amend entities.
-
Select a Dialog Resumption option:
- (Optional) Enable Amend Hidden Entities to allow amendment of entities marked as Hidden.
Task Level
- Go to Conversation Skills > Dialog Tasks → open the task.
- Click ⋯ (More Options) > Manage Amend Behavior.
-
Select Customize for this task:
(Optional) Enable Amend Hidden Entities at the task level.
Amend Trigger Patterns
The platform recognizes these utterance patterns as amend requests.~amend_synonyms includes: amend, change, modify, alter, update, replace, make, move, upgrade, want.
Multiple entity values can be amended in a single utterance. Example: “Change the departure date from today to tomorrow and departure city to Chicago.”