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.

Clients on Journeys can now set an expiration time for step up nodes to help reduce abandonment rates for step up verification. The timer tracks how long an applicant has been at the step up node. If the timer expires the user continues down an expired branch but if they complete step up before the timer they progress through the Journey as normal

To get started, navigate to your chosen Journey, click the ellipses on the step-up node and select “Set Expiration”. You can then set an expiration timeframe before hitting ‘Save’.

The What-If Analysis Testing results page has been updated to include: 

• a new summary section which displays things like the changes made and a table view into the outcome distribution
• Outcome rates on top of the bars in the graph to easily visualize the outcome rates before and after changes were made
• New filters to filter for original and test evaluations based on outcomes and tags.

Alloy now supports string outputs to better accommodate more complex credit policies and make the outputs more readable and accessible, minimizing client dev work.

String datatype can now be used as a possible output for:

Matrix Models

• When you’re setting up a Matrix Model, you’ll now see 2 datatype options from the drop-down. One of them will be “string”: this is referring to the cell outputs, not the axis header datatypes (note: those do not have to match the datatype of the cells).
• You can now edit the datatype of a Matrix Model after you create it - hit “Edit Matrix Model” from top right of the Edit panel.

Outputs Attributes

• When you’re creating a new Output Attribute, you’ll now see our new Attributes panel. You’ll see there are now 3 datatype options: Integer, Decimal, and String.

You should be able to create & use your “string” type output attribute in same way as integer-type that you are used to, except that you are limited to only 1 thing inside of the expression, and you can leave it empty (we’ll just return null in the API response if you do). You cannot use any of the math operators, of course! Just add 1 thing and that’s it. You can use JQ, however.