Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Summary:
Notification System updated to use .NET 6

Ticket:
NOT-310 - Getting issue details... STATUS

Detail
Notification System now uses .NET 6 thereby providing improved performance and security benefits.


Summary:
Notification System updated to use Angular 12

Ticket:
NOT-309 - Getting issue details... STATUS

Detail
Notification System now uses Angular 12 with improvements to its performance, form validation, and much more.


Summary:
Unassign users from the “Notification System“ application in Azure B2C when they are deleted

Ticket:
NOT-312 - Getting issue details... STATUS

Detail:
We maintain a list of applications each user has access to in Azure B2C. When a user is deleted in the Notification System, we remove the “Notification System“ from the list of applications the user has access to.


Summary:
SMS Notification - REST Testing Tool now shows the “TO” property

Ticket:
NOT-296 - Getting issue details... STATUS

Detail:
Users often use the REST Testing Tool when testing the Notification System API. When testing the SMS Notification API (POST /notifications/sms), it now shows the “To” property in both JSON and XML examples.


Summary:
”To" optional when sending a notification on the front end

Ticket:
NOT-313 - Getting issue details... STATUS

Detail:
Users now have the ability to set “CC“ OR “BCC“ email addresses without having to also set a “To” email address if a default “To” has already been set on Settings → Account Setup. This allow users to quickly send a notification on the front end using “CC“ OR “BCC“ without having to set a “To” email address when a default “To” already exists for this partners account.


Summary:
Ability to set a "Body" OR use a defined "Template" when sending a Notification (API and Front End)

Ticket:
NOT-298 - Getting issue details... STATUS

Detail:
Users now have the ability to set a "Body" OR use a defined "Template" when sending a Notification.
This can be done on the front end OR when using the API.


Summary:
Ability to paste a list of email addresses when sending a notification on the front end

Ticket:
NOT-315 - Getting issue details... STATUS

Detail:
Users now have the ability to paste a list of email address in the “To”, “CC“ OR “BCC“ text boxes separated by semicolon. Once they paste the list, they just need to press the tab key and the email addresses will be added.


Summary:
Ability to use the tab key to add email addresses on the front end

Ticket:
NOT-321 - Getting issue details... STATUS

Detail:
Users now have the ability to type in an email address in the “To”, “CC“ OR “BCC“ text boxes and then use the tab key to add the email address.


Summary:
Partner Accounts - Share SendGrid account and Webhook between different Partners

Ticket:
NOT-317 - Getting issue details... STATUS

Detail:
You can now share SendGrid details AND more importantly the “Webhook Endpoint“ for different partners.


Summary:
Switch between applications using the “Account” menu item

Ticket:
NOT-329 - Getting issue details... STATUS

Detail:
Users have the ability to view this list of applications and switch between these applications from the “Accounts“ menu item.


  • No labels