Event Message rules
In the base configuration, there is a single rule set—Event Fired—in the Event Message rule category. The rules in this rule set:
- Perform event processing
- Generate messages about the occurrence of events
PolicyCenter calls the Event Fired rules if an entity involved in a bundle commit triggers an event of interest to a message destination. A message destination registers an event to indicate its interest in that event.
As part of the event processing:
- PolicyCenter runs the rules in the Event Fired rule set a single time for every event of interest to a message destination.
- PolicyCenter runs the Event Fired rule set a single time for each destination that is listening for that particular event. Thus, it is possible for PolicyCenter to run the Event Fired rules sets multiple times for each event, one time for each destination interested in that event.
Warning
Be extremely careful about modifying entity data in Event Fired rules and messaging plugin implementations. Use these rules to perform only the minimal data changes necessary for integration code. Entity changes in these code locations do not cause the application to run or re-run validation or preupdate rules. Therefore, do not change fields that might require those rules to re-run. Only change fields that are not modifiable from the user interface. For example, set custom data model extension flags only used by messaging code.
Guidewire does not support the following:
- Guidewire does not support (and, it is dangerous) to add or delete business entities from Event Fired rules or messaging plugins (even indirectly through other APIs).
- Guidewire does not support—even
within the Event Message rule set—calling any message acknowledgment
or skipping methods such as
reportAck,reportError, orskip. Use those methods only within messaging plugins. - Guidewire does not support creating messages outside of the Event Message rule set.
See also