The following are key new features that have been delivered with Horizon 3.3:
Exporting contacts to secure locations
We have improved the security features associated with contact export; it is now possible to perform a contact export to a folder within an Amazon AWS S3 bucket as well as downloading it to the user’s machine.
This feature can be enabled at the account level within Account settings > Secure contact export. It is also possible to control, via permissions, whether a user has the ability to export to their secure S3 location.
The screenshot above shows the ‘Export to secure location’ button that will be visible when this feature is enabled and the user has the permission to perform a ‘secure’ export.
The Data management sub-menu on Contacts has also been re-labelled and a new menu option - Export summary - has been added.
This lists all exports that have been performed within the account and includes the username, export date, if a stored configuration was used and the destination of the export.
Two-factor authentication on user login and contact export
With release 3.4 it is possible to enable Dual-factor TOTP (Time-based One-Time Password) authentication against an account. When this is enabled (which is done within Settings > Account details) it will require a user to authenticate when they login and when they perform a contact export.
When logging in a user will be presented with the pop-up displayed on the next page. Once they have entered the requested code provided by their authenticator app they will be successfully logged in.
If TOTP authentication is enabled and the user wishes to perform a contact export they will also be asked to enter the 6-digit code presented by their authenticator app; see screenshot below.
Authorisation for user account management
Another security feature that has been added to 3.4 is the ability to require users to authenticate themselves when creating or editing user accounts.
This feature can be enabled at account level within Settings > Account settings > User Management. From here a user can enable whether authorisation is required to create or edit user accounts.
When creating new users, an authorisation from a designated ‘authoriser’ is required. To make a user account an authoriser requires their role to have the ‘Authorise’ permission on the User component (pictured below). When a new user account is created the authoriser will receive an email asking them to confirm the creation of the new user.
When a user edits an existing user account (their email address or phone number) the following pop-up will be displayed when they attempt to save the record.
On successful confirmation an email address will be sent to the user who has had their details changed, asking them to confirm the edit. Once they’ve done this the changes will be committed.
The following are some key improvements that have been delivered with HTK Horizon 3.4;
- Member level enhancements; several changes have been made to member levels; it is now possible to manually set them via the contact record, contact import process and via the Admin API. It’s also possible to return a member’s member level history via the Portal API.
- Added support for NOK, DKK and SEK currencies; transactions and currency to point conversions now support Norwegian, Danish and Swedish currencies.
- Online documentation for APIs; release 3.4 has introduced Swagger online documentation for Portal API and Integration API version R.
- Frequency of completion changes for custom behaviours; it’s possible to set frequency of completion in number of days or minutes.
- Viewing no. of matching active members for tags in a custom behaviour; it’s possible to see how many active members currently match the combination of tags used on a custom behaviour.
- Complete custom behaviours on behalf of member via Admin API; it’s possible to complete a custom behaviour on behalf of a member using the Admin API.
- Enhanced Points Expiration Date search and segmentation rules; search and segment criteria available for Point Expiration Date has been extended to include within the next [x] days, weeks and months.
- Configurable default text for manual point adjustments from CS portal; there’s now added flexibility to the control over the loyalty transaction activity description that’s applied when a manual point adjustment is made within the Custom Service portal. It’s possible, at the account level, to define a default description for a manual point addition or deduction and also specify if Customer Service users can edit the default text when they make an adjustment.
- Addition of an extra point expiry triggered messages; an extra ‘point expiry’ triggered message, with associated account settings, has been added meaning it’s possible to trigger up to two reminders to a member when their points are about to expire (i.e. 30 days from expiry followed by 7 days from expiry).
- Upgrade Mongo drivers and Morphia Versions to latest; upgraded key third party software components within the architecture to the latest versions.
The following customer affecting issues have been resolved in HTK Horizon 3.4:
- MS1 Cascade does not work correctly; an issue has been fixed within MS1 cascade functionality that was causing a second phone channel not to be dialled.
- Offer redemption count shows incorrectly; an error has been fixed that was causing a mismatch between the offer redeem counts shown against the offer and those showing on the loyalty redemption export.
- Loyalty members group points balance is larger than their actual point balance; Loyalty members’ group points balances were showing larger than their actual point balances due to transactions being processed whilst a loyalty member is suspended; this has now been fixed.
- You are unable to send test messages to contacts who are excluded from processing; it’s now possible to send test messages to contacts who have been marked as ‘exclude from processing’.
- Updating LIKERT_SCALES in loyalty profile doesn't work upon enrollment; an error has been fixed which was causing updates made to likert scale profile fields during loyalty enrollment to fail.