Triggers file

The configurable modifier triggers file defines sets of trigger conditions, each with an associated action configuration. If an operation is performed on an entity, and the operation satisfies the trigger conditions in any set, then the associated action configuration is run.

The configurable modifier has a single triggers file, in which you define all your sets of trigger conditions.

The configurable modifier triggers file has the following structure:

<triggers>
  <trigger wsrr-event=type_of_operation>
    <mapping>
      <entity>
        ... a set of trigger conditions ...
      </entity>
      <configuration name=associated_action_configuration />
    </mapping>
         .
         .
         .
    <mapping>
      <entity>
        ... a set of trigger conditions ...
      </entity>
      <configuration name=associated_action_configuration />
    </mapping>
  </trigger>
      .
      .
      .
  <trigger wsrr-event=type_of_operation>
    <mapping>
      <entity>
        ... a set of trigger conditions ...
      </entity>
      <configuration name=associated_action_configuration />
    </mapping>
         .
         .
         .
    <mapping>
      <entity>
        ... a set of trigger conditions ...
      </entity>
      <configuration name=associated_action_configuration />
    </mapping>
  </trigger>
</triggers>

You define one trigger element for each type of operation for which you want to define trigger conditions. You can define as many trigger elements as you want. The trigger element has the following attributes:

Attribute	Description
wsrr-event	The type of operation. The value must be one of the following: "create" "update" "delete" "transition" "make-governable" "remove-governance"
transition	The URI of the transition that an entity must undergo if the value of wsrr-event is "transition". This attribute is optional; if omitted, the trigger conditions apply to any transition operation.

Each mapping element defines a separate set of trigger conditions with an associated action configuration. Within each trigger element, you can define as many mapping elements as you want.

Within each mapping element, the trigger conditions are defined in an entity element, and the associated action configuration is defined in a configuration element. Descriptions of these elements, and an example triggers file, are provided in the following subtopics: