Events

Overview

When content is either published, updated, or when a user engages with that content through desktop or mobile notifications, specific events are triggered within the Heed platform. These events serve as pivotal moments that allow you to take further actions and customize behaviors based on the user interaction.

To harness the potential of these events, Heed provides the capability to create custom event handlers. These event handlers empower you to modify system behavior in response to these triggers, offering a high degree of flexibility and control over your content delivery strategy.

These events can be triggered by various key actions, including:

1. Heed Created: Events can be initiated when content is initially created within the Heed platform. This trigger allows you to set specific responses or actions when content is first generated, ensuring that your content delivery strategy starts on the right foot.
2. Heed State Transitioned: Events can also be triggered when the state of content transitions from one stage to another within Heed. For instance, when content moves from a draft to a final published state, you can create event handlers that respond to this transition, such as sending notifications or updating content accessibility.
3. Heed Attributes Updated: This event can be triggered when attributes related to content are updated. It provides the flexibility to customize actions in response to changes in content attributes, ensuring that your content remains up-to-date and relevant.
4. Heed Color Changed: When the color of your content is modified, this event can be triggered. For example when severity changes from Medium to High the color could change from amber to red.
5. Notification Sent: Events can also be triggered when notifications are sent to users. This provides an opportunity to track and respond to the distribution of notifications, ensuring that users receive the intended information.

When you create a new template in Heed, two default events are automatically generated to help manage the user experience effectively:

1. Expire Notifications When Heed is Closed: This event is designed to respond to the closure of the content. When the content state changes to "closed," any active desktop or mobile notifications associated with that content are automatically dismissed. This ensures that users no longer receive notifications related to content that has been finalized or concluded.
2. Expire Previous Notifications: This event is triggered when the content undergoes updates, and new notifications are sent out. In such cases, the previous notifications are automatically dismissed. This feature prevents users from receiving redundant or outdated notifications and maintains a clutter-free notification experience.

These default events provide essential automation and optimization within your content delivery process, ensuring that users receive timely and relevant information while reducing notification redundancy. Furthermore, the ability to create custom event handlers allows you to tailor Heed's behavior to your specific organizational needs, enhancing the overall efficiency and effectiveness of your communication strategy.

Accessing and modifying the Events

To access the events, follow these steps:

1. Open the Heed Admin Portal and click Create.
2. Find the template that you whish to update and then click on the edit pencil.
   
   
   
3. This will then open the message builder where you can edit the template. On the settings list on the righthand side, scroll down to Events and click on Modify.
   
   
   
4. In the Events modal, you should see a list of the configured events on the template. Typically, you will see at least the two default events.
   
   
   
5. You can then view and then modify an event by clicking on the event in the list.
   
   
   
6. You can then modify the event, disable it or delete it. 

Creating a new Event

To create a new event, follow the initial steps above to access the Events modal, then:

1. Click on New Event.
2. Enter a title and a description of your event.
   
   
   
3. Then, select when you would like the event to trigger from the When this event occurs dropdown.
   
   
   
4. You then have the option to add one or more condition for when the event should trigger. For example if we set the event to Notification Sent, we could choose the condition of the Heed Color changing to Green.
   
   
   
5. Then,under Perform the following activities, we can set to expire the notifications after 30 minutes.
   
   
6. Then finally, click Save and the template will be updated with the event.