Clients using portfolio monitoring can now run portfolio workflows on business entities, allowing them to better monitor the health of their existing customer base on an ongoing basis.
Please note: only one type of entity (e.g. person or business) can be evaluated in a single portfolio workflow.
To get started, simply select 'Business' as the Entity Type when creating a new portfolio workflow.
All clients leveraging Alloy Case Management to manage and file Suspicious Activity Reports (SAR) can now set up reminders in the dashboard to notify them to review the SAR and determine if a Continuing Activity Report that may need to be filed.
Financial institutions that file SARs with FinCEN may be required to file a continuing suspicious activity report after a 90-day review. To ensure reports are filed in a timely manner, clients can now set up reminders between 0-90 days for any SAR reports filed. Please note: reminders can only be set up for reports that have been accepted by FinCEN.
To set up the reminder:
All agents that have the permission to receive a SAR reminder will get one at the specified time. To update permissions, navigate to Settings > Roles > Case Management and tick/untick the box for ‘Agent can receive a reminder to review a previously filed report’.
Clients can now configure a name for input attributes. The defined names can be used and referenced in different parts of the platform and review experience.
All JQ-parsed input attributes that have a name defined in the workflow, will appear in the Rerun Application form. Clients who use the Rerun Application form to edit miskeys or other information during the review process will now be able to edit JQ-parsed input attributes in the form. The attributes will now appear in the form under Input Attributes section.
Please note: all existing attribute names have been backfilled with the JQ filter.
Clients using Allow and Deny Lists can now specify an expiration date when updating their lists to automatically approve or deny evaluations based on one or more PII elements for a given time period.
To get started, navigate to Settings, then select Denylist or Allowlist from the Settings menu. When adding record(s) to a list from the dashboard or via API, include a value for expires_at. When the list service is run in an evaluation, any values with ‘expires_at’ timestamps in the past will not be considered when denying or allowing.
Clients will now see a new Version Selector step that allows them to use the What-If testing tool from the Workflow Versions page and on a workflow version which has no unsaved changes. The Version Selector allows the user to select 1 other version of the selected workflow to test the current version against.
In the case that there are unsaved changes on the workflow and the user selects “Test”, the Version Selector will not appear if the user chooses not to create new test evaluations.
Clients using watchlist monitoring will now benefit from a new and improved watchlist review experience that will enable more efficient decisions on matching identities.
Clients can now gain access to more detailed information about potential watchlists hits to more quickly and accurately determine the course of action to take. With additional insights into match strength, matched fields, and reasons why the alert was generated, you can conduct high-quality investigations and make more informed decisions.
Decision on watchlist matches, whether individually or in bulk, and Alloy will maintain a history of those decisions for future decisioning. Suppress future updates for the matched identity to prevent false positives and ensure your teams are focused only on alerts that pose a true risk.
If you have any questions regarding these enhancements, ask an Alloy expert directly in LAB.
Clients using the Run App form can now copy and paste UBO information for business onboarding applications, helping to reduce manual entry and errors.
To get started, simply tick the box ‘Use this UBO as a representative’ when entering person-type entity details. You will then be prompted to add a representative when entering business entity details, which will pre-populate that section with the data previously provided. Alternatively, you can also enter business entity details first
Clients on Journeys can now configure Journeys webhooks with a specific journey and/or journey application event type scope. By default, Journeys webhooks will continue to apply to all journeys & journey application event types.
After selecting the live/sandbox journey application trigger action for the webhook, you can narrow the scope of the webhook by selecting specific journeys and/or journey application event types from the relevant dropdowns. Clearing out these selections will revert the webhook to the default behavior of applying to all journeys and journey application event types.
Existing webhooks will not be affected, however it is possible to update these existing webhooks with a more narrow scope.