Release Notes

Improvement

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

IMPORTANT

Sensedia API Management v5 clients: to obtain the authorization URL, import the Events Hub Authorization API.

Improvement

• Validation of the digital signature key for subscriber registration: when registering a subscriber on the Security screen, you need to validate a key to generate a digital signature.

  Previously, validating the key required accessing Postman and sending a POST request.

  Now, validation is done directly in the Events Hub without leaving the subscriber registration screen.
  Simply enter the key in the Key field and click VALIDATE KEY.

  See the Subscribers documentation for more details.

Improvement

• Event Status: when filtering by handlers on the Event Status screen, the Publisher and Subscriber fields now show only related results, making search refinement easier.

Improvements

• Status code: when registering a subscriber, you define the status code considered successful for event delivery.
  Previously, only 200-family codes could be entered. Now, you can use 2xx to cover the entire family.

  See more details in Subscribers – topics.

• Sorting: added the Order by filter on the Handlers, Policies, Publishers, and Subscribers screens. Choose between creation date or alphabetical order. By default, the most recent is displayed first.

• Import app: moved the Import from API Management button to the publisher creation screen. When clicking + Create Publisher, choose between importing an app or registering manually.

New feature

• You can now delete one or more events from the manual retry queue using the DELETE SELECTED button on the Delivery Retry screen.

Improvement

• Optimized the Delivery Retry functionality. Events in the manual delivery retry queue can now be automatically resent via the Event Status API.

  With this, you can implement automation to run delivery retries.

  To access it, go to Sensedia API Platform > API Design > API Catalog and search for "Event Status".

  Check out best practice suggestions for implementing this API in automatic retry.

Bug fix

• Adjusted the event preparation service so that, in topics with multiple subscribers, all receive events without sporadic failures.

Frontend adjustments

• Removed the Encrypt Body option from the Subscriber URL field.

Performance

• Improved execution and configuration layers for more efficient event handling.

Performance

• Improved the execution layer to optimize resource usage and overall performance.

Security

• Performed preventive maintenance on configuration and execution layers.

Bug fixes

• Adjusted the Delivery Retry system to avoid blank queries when the system took too long to respond.

Performance

• Implemented a new method for automatic retries for better performance and reliability.

Frontend adjustments

• Fixed the “Event ID” label (previously displayed as “Subscriber ID”) in the Event Status details pop-up.

Bug fix

• Correction previously omitted in version 1.2.1.0 for redirecting users without access.

Bug fixes

• Performance

  • Fixed an error that prevented the first event from being published for new clients.

  • Fixed internal event consumption to avoid losses after registration failures.

• JWT validation

  • JWT interceptor now correctly sends the token to the authorization server.

• Frontend adjustments

  • Adjusted the Event Status screen pagination with time filters.

  • Fixed the save button for context changes with linked topics.

  • Corrected various texts across multiple screens.

Bug Fix

• Adjusted the API Event Server service to ensure delivery to all subscribers, even when multiple are registered to a topic.

  Previously, if all automatic retry attempts for the first subscriber occurred before the event was sent to the other subscribers, their processes could be cancelled, causing event loss. Now, all subscribers will receive the events.

The Events Hub has a new look! We've adopted a more intuitive and visually appealing look & feel.

Check out the updates in the Events Hub 1.2.0.0 quick guide.

New features and improvements

• Contexts: new page in the main menu. Contexts act as logical markers in the publication URL, allowing topic reuse in different scenarios.

• Authorizations: renamed from Auth Settings and now in the main menu. Define authorization endpoints by context.

• Context enablement:

  • When creating grouped topics in a handler, you must enable all contexts where the topic can be published.

  • When registering or editing a publisher, the user must define, among all contexts enabled for a topic, which contexts will be available to the publisher. This ensures the publisher can only send requests to the topic in contexts available to them.

  • When registering or editing a subscriber, the user must define, among all contexts enabled for a topic, which contexts will be available to the subscriber. This ensures the subscriber only receives requests from the topic in contexts available to them.

• Random static token: generate directly on the subscriber registration screen (Security).

• Feedback: added a feedback submission field in the product menu. You can send a general feedback message or open a support ticket.

Bug Fix

• Adjusted automatic retries so that the configured number does not count the first attempt. If the user configures 5 retries and the first attempt fails, the Events Hub will automatically try a maximum of 5 times.

New feature

• New Delivery Retry page: resend failed deliveries only to selected subscribers.

Improvement

• The event list in Event Status now displays the event ID, number of subscribers, and retry history to facilitate manual retries.