Teneo Developers

Data Actions

After Match

After Match are actions which are executed and evaluated only after the trigger or transition has been triggered; this page provides information related to the various After Match data actions available in Teneo Studio, including step-by-step guides on how to add, edit or delete an action.

Types

The following After Match action types are available in Teneo Studio:

  • Entity
  • Language Object
  • Listener
  • Script

Read more in the Specifics section further below.

Add an After Match

Edit an After Match

Delete an After Match

Specifics

Multiple After Match data actions

Each User Intent trigger and transition can contain as many Data Actions as needed.

The matching process

Where Match Requirements are used to determine when a User Intent Trigger should trigger, Data Actions are those actions which are executed whenever the User Intent Trigger is triggered by a user input; so the Match Requirements need to match before the Data Actions will be evaluated.
As with Match Requirements, the Data Actions are executed in the same order as they are listed.

Entity Data Action

An Entity Data Action is executed only for inputs that match the selected Entity.
There is no mandatory connection between Entities matched in the Match Requirement list and those added to the Data Actions, i.e. Entity Data Actions can be defined even if no Entity Match Requirement is defined or even for different Entities.

When an Entity Data Action is added, it is possible to add a number of mappings from one of the NLU Variables of the Entity; every time a new input matches the Entity, the values in the source are stored in the selected targets. The same source can be selected multiple times, but each target can just be selected once (as multiple values would override previous ones anyway).

Language Object Data Action

The Language Object Data Action is executed only for inputs that match the syntax condition of the selected Language Object.
There is no mandatory connection between Language Objects matched in the Match Requirement list and those added to the Data Actions, i.e. Language Object Data Actions can be defined even if no Language Object Match Requirement is defined or even for different Language Objects.

When a Language Object Data Action is added, it is possible to add a number of mappings from one of the NLU Variables of the Language Object to Global or Flow Variables; every time a new input matches the Language Object's syntax condition, the value in the source is stored in the selected target. The same source can be selected multiple times, but each target can be selected only once (as multiple values would override the previous ones anyway).

Listener Data Action

The Listener Data Actions are activated whenever the User Intent Trigger or Transition is triggered and the TLML syntax of the Listener matches the user input. In those cases, the Groovy script expression of the Listener is executed.
The Listener Data Action subsitutes the former Trigger Post Listener; they are customizable with the same semantics as the previous Trigger Post Listeners.

Script Data Action

The Script Data Actions let the user execute Groovy scripts whenever the User Intent Trigger or Transition is matched.