Understanding action plug-ins

Action plug-ins enable you to interface with external systems, perform complex algorithms and manipulate situation graphs. When creating a knowledge model it is often necessary to communicate with external systems. This may involve connecting to a database, reading from a message queue or sending an email. All of these actions this can be performed with action plug-ins. It may also be necessary to perform complex mathematical algorithms that it does not make sense to model in the Erudine Behaviour Engine. Again, these can be incorporated into your knowledge model through action plug-ins. When connecting to external systems or performing algorithms it is often necessary to insert the data retrieved or calculated into the situation graph. Unlike functions, action plug-ins allow you to add your results to the situation graph, either as a single concept or even in a graphical structure.

Action plug-ins run after all conventional behaviour processing for a node has completed. This means that the action plug-in author is able to perform their calculations on the output situation graph that incorporates the behaviour of the node.

The Erudine Behaviour Engine contains a number of standard action plug-ins that are ready to use with any knowledge model. The following table lists all the action plug-ins that are shipped with the Erudine Behaviour Engine.

Name Description
DeleteEntity Directly deletes data from a database based on the configuration of an entity.
InsertEntity Directly inserts data into a database based on the configuration of an entity.
ReadEntity Extracts data directly from a database based on the configuration of an entity. Always inserts a graph into the situation that represents a single result.
UpdateEntity Directly updates the data on a database based on the configuration of an entity.
MaxDate Extracts the latest date from concepts within the conceptual graph.
MinDate Extracts the earliest date from concepts within the conceptual graph.

The simple action plug-in

The implementation of action plug-ins can be quite complicated. In order to make this process easier, Erudine provides an abstract, simple action plug-in that defines much of the common behaviour. When creating an action plug-in, therefore, it is worth considering whether the simple action plug-in is sufficient for your needs. Of course, there is no obligation to use the simple action plug-in and thus the implementer retains a powerful tool for extending the Erudine Behaviour Engine.


Platform: all
EBE Version: 2.4
Category: Development Reference Guide
Author: Patrick Peisker


Browse Space

- Pages
- News
- Labels
- Attachments
- Bookmarks
- Mail
- Activity
- Advanced

Explore Confluence

- Popular Labels
- Notation Guide

Your Account

Log In

 

Other Features

Add Content