Teneo Developers

Ordering suggestions


The Suggest Ordering feature can automatically generate suggestions for ordering relations, propose removal of spurious relations, identify Intent trigger issues which can't be solved by simply adding or deleting ordering relations and finally can suggest actions on how to resolve these. The Suggest Ordering feature is based on Auto-test results which means that the reliability of this feature depends on the quality and coverage of the examples of User Intent added to each Intent trigger in the solution and that it is limited to the Auto-test's inability to evaluate embedded script syntaxes.

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.

Suggest Ordering

There are three available buttons which each allows to run the Suggest Ordering with different scopes:

  • Filtered: runs Suggest Ordering on Intent triggers which match the currently enabled filter(s)
  • Selected: runs Suggest Ordering on currently selected Intent triggers and/or Order groups
  • Solution: runs Suggest Ordering on all Intent triggers in the solution


When Suggest Ordering has finished, Teneo Studio generates notifications of two types in the left-side panel of the Ordering window:

  • Suggest Ordering Problems which covers the detected issues which Teneo cannot solve on its own; these notifications should be closely reviewed by the Teneo Studio user
  • Suggest Ordering Changes which displays the changes performed by the Suggest Ordering feature

Suggested Ordering Problems

The first part of the notifications provides a resume of the Suggested Ordering Problems, which 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 of User Intent in a Flow doesn't match its own Matches. To resolve this, either update the Matches of the Intent trigger to cover the positive example or delete the example from the Flow if it is no longer needed.

Read more about Matches in the Flow section

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.

Triggers in Different Groups

Mutually matching examples

Mutually matching examples occur when two Intent triggers have an example of User Intent 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 Matches need to be edited.

Mutually Matching Examples

Read more about Matches in the Flow section

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.

Cyclic dependency

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.

Suggested Ordering Changes

The Suggested Ordering Changes cover the changes which Teneo automatically applied while running the Suggest Ordering feature which are divided into the following categories:

  • Deleted relations
  • Added relations

The user can click the right-pointing arrow to select the affected triggers and view the changes in the main view or revert the changes done by Teneo by clicking the Re-create this relation button or the Remove this relation button.

Suggest Ordering Changes