What’s New

Events Hub authorization API: only authorized publishers can send events to Events Hub. To authorize publishers, you have to configure the authorization URLs.

Validation of the digital signature key when registering subscribers: when registering a subscriber, on the Security screen, you need to validate a key to generate a digital signature.
Before, to validate the key, it was necessary to access Postman and send the call through a POST request.
Now, validation is done in Events Hub itself, without having to leave the subscriber registration screen. Just add the key in the Key field and click the VALIDATE KEY button.

Event Status: now, when you select handlers in the filter of the Event Status screen, the fields Publisher and Subscriber will show only the results related to them. This way, it will be easier to refine the search.

Status Code: When you sign up a subscriber, you choose the status code that shows the event delivery was successful. Before, you could only use a 200 family code. Now, you can use 2xx to cover the whole family. Check the Subscribers documentation for a better understanding.

Ordering: we’ve added the Order by filter to the Handler, Policies, Publishers and Subscribers screens. With it, you can choose whether you want to view the registers by creation date or alphabetically. By default, we’ll show them from the most recent creation to the oldest.

Import app: we’ve moved the Import from API Management button into the publisher creation screen. This way, when you click + Create Publisher, you can choose to import an app or register the publisher manually, on the same screen.

Now you can delete one or more events from the manual retry queue via the DELETE SELECTED button on the Delivery Retry screen.

We improved the Delivery Retry feature. Now, events that fall into the manual delivery list can be resent automatically through the API Event Status. With it, you can set up an automation to run delivery attempts.
To access it, go to Sensedia API Platform  API Design  API Catalog and search for "Event Status".
Check our best practice suggestions to use that API in Retry Delivery.

The service responsible for receiving and preparing the events that need to be delivered to the subscribers was fixed. When this service prepared the necessary information for sending the message in a topic that contained more than one registered subscriber, it was observed that an error occurred sporadically while delivering the message to one of the subscribers. Now, all the subscribers will receive the events.

We removed the option Encrypt Body from the field Subscriber URL.

We improved the execution and the configuration layers to handle the events more efficiently and to make better use of the resources employed by the application.

We improved the execution layer to handle the events more efficiently and to better use the resources employed by the application.

We have performed preventive maintenance in the configuration and execution layers.

We made a change in the system behind the Delivery Retry screen to mitigate some cases in which the system did not respond in the expected time and showed a blank query.

We have changed the method used for automatic retries in order to improve the performance and reliability of the process of sending events.

We have fixed the "Event ID" label on the Event Status screen, as the "Subscriber ID" was being displayed within the event detail pop-up.

The service API Event Server has been fixed for situations in which an event is sent to a topic with more than one registered subscriber. Before, if all the automatic retries related to the first subscriber occurred before the event had been sent to the other subscribers, these last processes would be cancelled. This resulted in the loss of events. Now, all subscribers will receive the events as expected.

We’ve added a new feature, with its own page in the main menu: Contexts. Contexts are a logical division that serves as a placeholder for the event publication URL. They allow topics to be reused in different usage scenarios.

The Auth-settings screen (which was found in Integrations  Auth Settings) has been renamed to Authorizations and is in the main menu. It’s now possible to define publisher authorization endpoints for each context.

Due to the new contexts feature, the processes of registering handlers, publishers and subscribers now include enabling contexts.

In the security step of subscriber registration, it’s now possible to generate a random static token on the Events Hub screen.

We have included a field for sending feedback on the main menu. You can either send a more general feedback message or open a support ticket.

The behaviour of automatic retries has been fixed. Before, if a user set 5 retries on the configuration of policy, Events Hub included the first attempt in this number. Then, we would have the first attempt and 4 automatic retries. Now, the total registered does not include the first attempt. That is, if the first attempt fails, Events Hub will automatically retry sending the event up to 5 times.

We included a new page in the main menu: Delivery Retry. It allows making new delivery attempts to only the subscribers that you select.

The list of events on Event Status now displays more information: event id (to make it easier to manually retry deliveries), quantity of subscribers and a history of delivery attempts.