AVC or Attribute Value Change is a type of notification which the Ticketer sends to the carrier as opposed to the request based actions from the carrier that we have discussed thus far. These notifications are generated via Domain events. The two types of domain events that we are currently tracking are PostInsert and PostUpdate. This field is narrowed even further by the fact that we are targeting specific domains in relations to these events. The domains which are being tracked are described in more details below:

Ticket:

• Only tracking PostUpdate events on this domain.
• Examples of Ticket domain PostUpdate events would be ticket status changes, closed_date population.

FormValueChange:

• Only tracking PostInsert events on this domain.
• FormValueChange inserts only happen on form fields which have the Boolean trackInRunningLog set to true.
• In the case of eBonding the only field that we are monitoring currently for a PostInsert event on the form is carrier_update.

The class which listens for these PostInsert and PostUpdate events is called AuditProvider. It extends AbstractPersistenceEventListener, which is a grails class which implements PersistenceEventListener.

After an update occurs on the Ticket domain or an Insert occurs on the FormValueChange domain, a JSON object is built. This JSON object contains information including the old value, new value, event type, changed properties, domain, ticket id and full object. This JSON object is passed onto an exchange, to which the ebonding_component is subscribed to. From here the AVC is processed and sent onto the soap_component and form there to the carrier in the form of a soap response.

For a detailed diagram of the AVC architecture see Figure 8 below: See Figure 8:

Figure 8