CUE Live Transaction Filters

A transaction filter is a user-defined function that gets executed whenever certain operations (or transactions) are performed, and can thereby modify the outcome of those operations. It is a standard Content Engine mechanism for modifying and extending Content Engine behavior, and is described in detail in the Escenic Content Engine Advanced Developer Guide.

The CUE Live can also be extended/modified using transaction filters. The main reason you might want to make use of them would be in order to integrate CUE Live with an external system in some way: for example to copy all CUE Live events to an external system as they are created.

The CUE Live transactions that can be modified using transaction filters are:

  • Object creation

  • Object update

  • Object deletion

A transaction filter is implemented as a Java class. A transaction filter can, for example:

  • Modify a CUE Live entry as it is being saved

  • Prevent a CUE Live entry from being deleted unless certain criteria are met

  • Perform additional actions when a live entry has been created