App Events

Succeed Insurance is looking to see how they can send data to external systems as different entities change within each Guidewire application. They had heard App Events may be a way to do that.

Learning Objective

The learning objective for this module is to explain the basic functionality of App Events.

Overview

App Events is an essential part of the Guidewire Integration Framework that represents the new approach for outbound integrations between InsuranceSuite and external systems. App Events enable downstream systems to subscribe to business events and receive up-to-date claim and policy information in near-real time without coding.

App Events support two delivery mechanisms:

• App Events Webhooks

A User Interface (UI) that provides customers with a no-code way to subscribe external systems to events occurring in the InsuranceSuite application.

• Integration Gateway

Integration Gateway apps deliver events to external systems using protocols that Apache Camel supports. Developers write Camel routes to read events and invoke routes when events occur to deliver them to recipients.

App Events acts as an outbound API for ClaimCenter and PolicyCenter. It makes it easy to publish events and full claim graph snapshots from the InsuranceSuite apps to downstream systems such as external applications, internal systems, and third-party services.

Downstream systems need to be notified of business events occurring in an InsuranceSuite app. For example, a medical bill review system needs to know when injury claims and medical exposures are opened, an auto physical damage system needs to know vehicle claims and incidents are opened or updated. Another example, a billing system needs to know when a new policy is created or and an existing policy is changed. These kinds of integrations are known as outbound asynchronous delivery.

Traditionally, in InsuranceSuite implementations, developers use event messaging with Gosu rules and custom message transport plugins to send messages from InsuranceSuite to external applications. Consequently, changes to this integration logic require Gosu changes. The new App Events framework enables event-driven, outbound asynchronous integrations without requiring custom Gosu code. This allows integration logic changes to be made to a different lifecycle outside of the InsuranceSuite application changes.

Guarantees

App Events provides several important guarantees concerning event delivery:

• Events are delivered at least once.

• Events are safe-ordered by the primary object that they are associated with.

• Webhooks subscriptions and Integration Gateway Camel route subscriptions are isolated. If a Webhooks endpoint goes down, it does not affect the delivery of other subscriptions. If a Camel route cannot deliver to an endpoint, it does not block other Camel route deliveries.

• Consumers do not affect the performance of InsuranceSuite. A consumer is a downstream system that consumes or reads application events.

Additional information

There is a course that provides more detail on App Events and lets you get hands-on experience with them. It is part of the current Insurance Suite Cloud Integration track.