Skip to content

The BizzStream Event Framework

As the name indicates, the BizzStream Event Framework facilitates the handling of events. Events are occurrences in the environment, that require a response. The primary purpose of the event framework is to manage these events in a structured and efficient manner.

Event

An event can be thought of as a signal that something significant has occurred within an environment. Events are the way in which a model can notify that a specific occurrence has taken place, often requiring some form of response or processing. Event handlers are notified when an event takes place.

Event listeners

Event listener are designed to respond to events. When an event occurs, the corresponding event listener is triggered executing its code asynchronously to process or react to the event.

Getting Started with Events

Ready to leverage events and streamline your workflow? Here’s a simple guide to get you started:

  1. Define Your Goal: What do you want to accomplish with events? For instance, you might use them to handle saving information.
  2. Create Your Event: Learn how to create and trigger events. Explore the various options available, including using the Emit Event action rule as demonstrated in the workflow example.
  3. Personalize Your Event Data: Events can carry valuable information. Structure your JSON data to include all necessary details. Remember, you can utilize Bizzstream expressions here.
  4. Set Up an Event Listener: Discover how to create event listeners in our documentation. Ensure the listener is configured with the correct event name.
  5. Test Thoroughly: Before widespread implementation, always test your event setup to confirm everything is working as expected.

Advantages of using the event framework

There are several advantages of using events and event listeners:

  • Events allow for a separation between the source of an occurrence and its response. This means that different parts of the model can operate independently, only interacting through well-defined events and responses. Such decoupling enhances modularity and maintainability of your model.

  • Because event listeners execute asynchronously, the model can remain responsive and efficient, while handling time-consuming operations, by processing events in a non-blocking manner.