You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, blocks in Hexabot can be triggered by NLU entities (intent, keyword entity values, etc.). However, when multiple blocks match based on NLU entities, there is no clear prioritization strategy.
This feature request aims to prioritize the block with the highest number of matching NLU entities, ensuring that the most relevant block is triggered. Additionally, trait entities should have a higher priority over other types of entities.
Acceptance Criteria:
When multiple blocks match based on NLU entities, the block with the most matches should be triggered.
Trait entities should take priority over other entity types in determining the next block.
Ensure that the existing NLU-based block triggering mechanism remains functional.
Add unit tests to validate the prioritization logic.
To be ignored:
If multiple blocks have the same number of matching entities, fallback to an explicitly configured priority (if available).
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Description
Currently, blocks in Hexabot can be triggered by NLU entities (intent, keyword entity values, etc.). However, when multiple blocks match based on NLU entities, there is no clear prioritization strategy.
This feature request aims to prioritize the block with the highest number of matching NLU entities, ensuring that the most relevant block is triggered. Additionally, trait entities should have a higher priority over other types of entities.
Acceptance Criteria:
To be ignored:
The text was updated successfully, but these errors were encountered: