Teneo Developers

Ordering suggestions


The Suggest Ordering feature automatically generates suggestions for ordering relations, propose removal of spurious relations, identifies Intent Trigger issues which can't be solved by simply adding or deleting ordering relation and finally suggests actions on how to resolve these.

The feature is based on Auto-test results, which means that the reliability of this feature depends on the quality and coverage of the examples added to each Intent Trigger in the solution and that it is limited to the Auto-test's inability to evaluate embedded script conditions.

The Suggest Ordering performs the following changes:

  • Adds ordering relations between Intent Triggers within the same Order group when justified by Auto-test
  • Deletes unprotected ordering relations when these are not needed according to Auto-test results
  • Creates notification for the user regarding Auto-test failures which the user should review.

Run Suggest Ordering

In the Home tab of the Intent Trigger Ordering window, the user will, in the top ribbon, find the Suggest Ordering area.

There are three available buttons:

  • Filtered
  • Selected
  • Solution

Suggest Ordering can be run on the currently enabled filter(s), the currently selected Intent Triggers and/or Order groups, or on all Intent triggers in the Solution.


When Suggest Ordering has run, Teneo Studio generates ordering notifications for possible issues which the Suggest Ordering feature itself cannot solve. These notifications should be reviewed by the Teneo Studio user.

These issues covers the following categories:

  • Non-matching examples
  • Triggers in Different Groups
  • Mutually matching examples
  • Cyclic dependency
  • Protected relations in wrong direction.

Non-matching example

The Non-matching example notification appears if a positive example in a flow doesn't match its own match requirements. To resolve this, either update the match requirements of the Intent Trigger or delete the example.

Triggers in different groups

If an Intent Trigger from a lower ranked Order group needs to be evaluated before an Intent Trigger in a higher ranked Order group, the suggestion is to move one of the Intent Triggers to the other Intent Trigger's Order group so that the needed relation between them can be added.

The user can use the blue arrows, next to the notification, to move one of the Intent Triggers up or down, or manually move one of the Intent Triggers in the main view.

Mutually matching examples

Mutually matching examples occur when two Intent Triggers have an example question which matches not only the Intent Trigger it belongs to, but also the other Intent Trigger.

To resolve this, the example and or the Intent Trigger's match requirements need to be edited.

Cyclic dependency

Although uncommon, it can happen that a relation is created from Trigger B to Trigger C to Trigger A and then again from Trigger A to Trigger B. This is a cyclic dependency.

The Suggest Ordering feature checks for these kinds of cyclic dependencies and notifies the user about which Intent Triggers are involved.

A cyclic dependency is highlighted in red (rather than orange) in the Intent Trigger Ordering view (see above image).

Itmay not be the red-marked relation that is erroneous, but rather one of the other relations in the cyclic loop. The system has no way of determining which of the relations in a cyclic loop should be removed.

Protected relation in wrong direction

Suggest Ordering also detects when a protected relation might have a wrong direction. Since relations are usually protected for a good reason, the corresponding notification will not change this but rather suggest the user to have an extra look at it.