Intent Event Listener
Introduction
An intent event listener allows an AI to trigger a certain action within a case. This event listener is used in combination with an Orchestrator Agent.
Properties
General
Attribute | Type | Description | Category |
---|---|---|---|
Model Id | Text | Model Id identifies the element within the process model. | The model id, name and documentation properties are used to uniquely identify the intent event listener, to give it a user-friendly name and to add a free-form description. |
Name | Text | The name of the element. This is the name displayed in the diagram. | |
Documentation | Multiline Text | The documentation attribute additionally adds a description to the component. | |
AI instruction | Multiline Text | An AI instruction that provides additional instructions to the orchestrator agent. The more details here, the more applicable the responses will be. | Allows to specify instructions towards the underlying orchestrator agent. The instructions added here will be added to the prompt when evaluating which intent should be triggered. |
Advanced
Details
Attribute | Type | Description | Category |
---|---|---|---|
Available condition | Text | Sets an available condition, which is an expression that moves the event listener into the available state after creation if true. Also returns the event listener back to the unavailable state when the condition becomes false again. | The life cycle of event listeners is simpler than that of plan items such as human tasks: an event listener stays in the available state until the event happens. There’s no active state like for other plan items. In some use cases however, the event listener shouldn’t be available for the user to interact with unless a certain condition is true, typically based on case instance variables. The available condition serves exactly that purpose. |
Include in history | Boolean | When the history level is set to "instance" or "task" level with this property it can be configured if this plan item instance should be included in the historic plan item instance data. | The Include in history flag can be used to store the historical entry of this intent event listener when running with a history level that normally would not store the execution of the plan item. Note that this flag has no effect when running with history level 'none'. |
Listeners
Attribute | Type | Description | Category |
---|---|---|---|
Lifecycle listeners | List | Allows you to define lifecycle listeners for a plan item. Lifecycle listeners allow you to execute an expression, a delegate expression or a class when a plan item transitions from one state to another. | With lifecycle listeners it is possible to react to state changes of this intent event listener. Lifecycle listeners allow you to execute an expression, a delegate expression or a class when the plan item instance transitions from one state to another. |
Visual
Attribute | Type | Description | Category |
---|---|---|---|
Font size | Selection:
| The font size of the element in the diagram. | Visual properties that determine how the intent event listener is shown in the diagram. This has no impact on the runtime execution. |
Font weight | Selection:
| The font weight of the element in the diagram. | |
Font style | Selection:
| The font style of the element in the diagram. | |
Font color | Color | The font color of the element in the diagram. | |
Background color | Color | The background color of the element in the diagram. | |
Border color | Color | The border color of the element in the diagram. |
List Attribute Details
Lifecycle listeners
Attribute | Type | Description |
---|---|---|
Source state | Selection:
| |
Target state | Selection:
| |
Class | Text | Fully qualified classname of a class to be invoked when executing the task. The class must implement either PlanItemJavaDelegate or CmmnActivityBehavior. |
Expression | Text | JUEL Expression to be executed when the task is started. Expressions allow you to interact with the backend by calling services, making calculations etc. You can find more information about expressions in the documentation. |
Delegate expression | Text |