Fill this in

Event Properties

As well as the standard properties that can be set on all events, the following properties can be set on this type of event:

 

Property

Description

Target Type

The type of biskits whose creation, deletion or update triggers this event.

Create Events

true if an this event should be triggered by the creation of a biskit, and false if we should ignore biskit creation events.

Update Events

true if an this event should be triggered by the update of a biskit, and false if we should ignore biskit update events.

Delete Events

true if an this event should be triggered by the deletion of a biskit, and false if we should ignore biskit deletion events.

Vetoable Events

When a database event occurs, you sometimes want to run inside the database transaction so that you can modify the data before it is saved or so that you can prevent (or veto) the database change. But you sometimes would prefer to be outside the database transaction so that the event is triggered only after the database change has completely finished. Set this optionto true if we should run inside the database transaction and so have the option of preventing the transaction from completing, and false if we should run after the transaction has completed.

 

Properties Available for Child Actions To Use

The following properties are available for use in any child or descendant action:

 

Properties

Notes

new

The new value of the biskit after the change. old and new are identical for a create and a delete.

old

The old value of the biskit before the change.

AuditLog

Information stored in the AuditLog for this change. This records information about who made the change, when, and what the biskit was like after the change.

UserMakingTheChange

Indicates which user made the change.

Crud

Property storing the type of change Create, Update, Delete.