FraudShield Release v1.4.1
3 New3 Improvements4 Changes2 Fixes
This release introduced dynamic filtering, multi-factor authentication, and a new preference for controlling empty field visibility.
| Type | Feature | Description |
|---|---|---|
| New | Dynamic Filtering | Most pages now support multiple simultaneous sort options for filtering results. |
| New | Multi-Factor Authentication | Users can now secure their account with a time-based one-time password generated by an authenticator app. |
| New | Hide Empty Fields | A new preference controls whether empty fields are shown or hidden when viewing transaction and customer details, with an inline toggle available on each page. |
| Improvement | Cases | Case exports now include full transaction details alongside case information. |
| Improvement | AI Rule Builder | Generates more accurate and consistent rules across a broader range of fraud scenarios. |
| Improvement | Audit Logs | JSON comparison logic for audit log entries has been updated for improved visibility. |
| Change | Reference Lists | The description field is now required when creating or editing a reference list. |
| Change | Empty Integer Fields | Empty integer fields now display as blank rather than 0. |
| Change | Default Rule Plan | The default rule plan now uses a curated set of high priority rules. |
| Change | Rule Plans | Limits each rule plan to a maximum of 50 rules. |
| Change | Submit Single Transaction API | Removed the mappingID parameter from the Submit Single Transaction API. |
| Fix | Form Validation | Fixed an issue where the screen did not snap to fields with validation errors on form submission. |
| Fix | Cases | Fixed an issue where address line 3 was missing from case report exports. |
This release also includes minor performance improvements, bug fixes and internal updates.