1. Release Notes - Notification Hub 1.0
Release date: TBD
1.1 New features
The Notification Hub, from now on referred to as 'NH', allows you to configure the notifications that will be pushed to your Connective solution. In version 1.0 of NH, your "Connective solution" is always eSignatures 6.0.
The notifications are sent users every time they must be notified. For instance when their account has become available, when they need to approve or sign a document, etc.
Prior to the NH, notifications were managed in the backend code of the Connective solutions themselves.
Out of the box, NH offers plain text templates. You can also configure HTML templates however.
The NH offers the following advantages:
- Notifications can be sent via SMS, instead of only via email.
- Notifications can now be customized much more easily through a Configuration Index and the NH API, instead of having to modify them in the backend code.
- NH supports HTML emails, to create rich and responsive email messages. Two sets of HTML templates are available at Connective, that can be further customized to your liking: one Connective themed and one general themed. To obtain your sets of HTML templates, contact Connective at email@example.com. The sets of HTML templates will be delivered in a .json file that can be used in the NH API through applications such as Postman.
NH is a multitenant application, which offers multiple operational cost efficiency advantages.
1.2 Removed features
1.3 Handled issues
1.4 Known issues
Notification Hub 1.0
|Jira code||Issue code||Description|
|CNH-93||/||When hosting the NH in IIS under /NotificationHub, its Config Index does not work.|