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.

Both codeless SDK and legacy SDK users can now autonomously create keys directly in the dashboard. 

Clients will also be able to see all available device and behavioral risk service settings on this page.

Codeless SDK users can also associate keys with Journeys to allow them to have different customization options for different Journeys (i.e. one Journey is for onboarding and one is for credit underwriting so the outcome screen text differs). 

To get started, navigate to Settings > SDK where you’ll see the updated SDK page.

Clients on Journeys will now see an ‘Archive’ button to help for all action nodes (including custom Review nodes), that will show a new warning modal, listing all of the active Journeys which that action is used in. This will help reduce potential errors when making changes to your Journey.

We have also added a new Journey Builder Validation error in the journey graph on the archived action nodes, so that they will be easy to spot. This will also ensure you won't be able to set a new journey version active or clone it if it contains archived action / Review nodes.

Clients on Journeys can now test their policies end-to-end to validate that they function as expected and that they’re receiving the desired outcomes.

A multi-environment configuration will allow clients to specify the credentials or sandbox settings for each service used within a Journey version. Additionally, outcomes can be set for action and step-up nodes to auto-complete these steps since a user action is required in a real life setting.

To get started, you can access the Multi-environment Configuration through the Journey’s Testing Suite.