06 February 2023 (v2.86)

ReachFive v2.86 brings improvements to export jobs, audit logs, and lite profiles as well as bringing additional functionality to our Login as feature. We also worked on a few other improvements. And of course, we fixed a few issues.

Export path variables

You can now add variables to your export path for exporting profiles, consents, or events. This improvement aims to give you more control on file naming for your exports and helps better organize these for analysis.

For more on these new export path variables, see the Export job definitions page.

Audit logs

We added a new action (settings:update) for audit logs so that whenever a setting is altered or a feature is enabled or disabled, an audit log is produced.

For more on audit logs, see Audit logs.

Lite profiles

We have improved the logic for when you update unified profile identifiers so that updates to the managed profile propogates to the lite profile.

For more on lite profiles, see LITE registration.

We bring additional functionality to the Login as feature. Now, you have more control over the configuration for particular users with a dynamic mode. You are, of course, still able to configure a global setting for logging in as a user, but this improvement gives you more options.

For more on the Login as feature, see our Login as guide.

Other improvements

We have enhanced the validation process for emails in the UI SDK to make sure all legitimate values are accepted.
We have improved the loading time for job definition and job reports list pages.
For consent logs, we tweaked the query to make sure they are displayed in descending order from the newest to oldest.
Our Filtering function has improved to ensure you see all relevant results directly in the ReachFive Console.

Fixes

Item Fixed

Item	Fixed
In some limited cases, it was not possible to connect when `display` was set to `popup` mode during a social login flow.	✓
In some instances, you could not use a `custom_identifier` with Hosted Pages.	✓
Hosted Pages were not updating the `origin` field as expected.	✓
It was briefly possible to choose consent groups when setting up an export where only standalone consents should be selectable.	✓
Sometimes, Azure accounts were inadvertently deleted when there were two user accounts associated with different Azure Active Directory organizations on the ReachFive Console.	✓

In some limited cases, it was not possible to connect when display was set to popup mode during a social login flow.

✓

In some instances, you could not use a custom_identifier with Hosted Pages.

✓

Hosted Pages were not updating the origin field as expected.

✓

It was briefly possible to choose consent groups when setting up an export where only standalone consents should be selectable.

✓

Sometimes, Azure accounts were inadvertently deleted when there were two user accounts associated with different Azure Active Directory organizations on the ReachFive Console.

✓