Risk Analytics April Release 22.R2

All exported files produced by the Risk Analytics Presentation Service now specify the character used as a value separator (a semicolon ";" character) in their header, to avoid a parsing mismatch when reopening these files with CSV editors.

This applies to the CSV export of console logs in the Export/Import and Environment pages, and the reports generated or scheduled in the Reports page.

To keep Risk Analytics up to date, we have added support for the Edge browser, and removed support for Internet Explorer 11.

Risk Analytics now supports the Chrome and Edge browsers.

When running a rule test for historical events, the result of the test was unexpectedly impacting the further review of these events in the Event Detail screen. A rule that matched for these events during the rule test was added in the list of matched rules in the Event Detail screen.

This issue has been fixed.

Ampersand "&" characters in the value of some string fields were causing failure on the daily factor computation when sending events to Risk Analytics, inducing multiple computation retries that caused high database load and decreased performance.

This issue has been fixed.

When an event with a missing or empty field value was tested against campaign, division, or rule criteria for not being part of a hotlist, there was a discrepancy depending on whether the hotlist was empty or not. A criteria testing if such a field was not in a given hotlist was correctly evaluated as TRUE if the hotlist was empty (contained no records), but was wrongly evaluated as FALSE if the hotlist did contain any records.

This issue has been fixed.

This issue, and the corresponding fix, are relevant only for customers using the NOT IN or NOT EXISTS hotlist clause in campaigns, divisions, or rules.

It is important to highlight that existing campaigns, divisions, and rules using the NOT IN or NOT EXISTS hotlist clause will not automatically be fixed after the Risk Analytics version update. Only new campaigns, divisions, and rules, or ones modified after the update, will use the fixed algorithm. To fix an existing campaign, division, or rule, just edit it in Presentation Service and type in, for example, a small change in description prior re-saving it.

Please note that compiling a complete hierarchy (Non Mon Events, Transactions...) will not be sufficient to regenerate campaigns, divisions, and rules with the fixed algorithm.

Some mobile non-monetary events or transaction fields collected in the mobile CDDC clear data were not correctly mapped and were not received and stored by Risk Analytics as expected:

• BLUETOOTH_DEVICE_LIST

• BOUNDED_BT_DEVICE_LIST

• DEVICE_MODEL

• WIFI_BSSID_LIST

• CONNECTED_BT_DEVICE_LIST

• CONNECTED_BSSID

• MOB_APP_RELEASE_DATE

• NETWORK_NAME

• KEYBOARD_ID

• LAUNCHER_ID

• MOB_TIMEZONE

This issue has been fixed.