New features and enhancements
New response code to trigger biometric authentication
To enhance biometric authentication via mobile application and allow the mobile application so select the most relevant biometric method, a new response code has bee added, ChallengeBiometric. This is available for rule configurations and triggers biometric authentication via mobile application in orchestration-based flows.
Fixes and other updates
Issue OSRAC-6927: Match key assignment unclear (Presentation Service)
Description: In the Rule Management page, the display of match criteria for a rule could be misleading because it was unclear which match key applied to a given criterion.
Status: This issue has been fixed. A new Match Criteria column has been added to the Match Keys table to clearly indicate the criterion associated with each match key.
Issue OSRAC-6945: Time zone mismatch in hot list entry expiration (Presentation Service)
Description: When a hot list entry is created with expiration date, the entry expires at the defined data and time but the Risk Management Component incorrectly used the time zone of the database server. For the user, this lead to erratic user interface behavior when entering data in a hot list.
Status: This issue has been fixed. The expiry date field now uses UTC time zone entries.
Issue OSRAC-6972: Unexpected user log out from Presentation Service
Description: The user may have been unexpectedly logged out from Presentation Service, even though the inactivity timer threshold had not been reached.
Status: This issue has been fixed.
Issue OSRAC-7004: Matched rule details for event not displayed (Presentation Service)
Description: On the Event Details page, the Matches table showed no entries even when the event matched one or more rules.
Affects: Versions 26.R1 (3.0.1) and 26.R2 (RA 3.0.2)
Status: This issue has been fixed. The Matches table now correctly lists every rule the event matches.