Clients on Journeys have access to several improvements to better identify and navigate rerun Applications:

• Filter the Application Queue to distinguish rerun Applications from original Applications for audits and reporting.
• New rerun indicator on the Application details page to easily identify rerun Applications.
• Hyperlink related Applications, allowing agents to easily navigate to previously run Journey Applications and the original/source Journey Application.

Clients utilizing Alloy’s Events API now have another level of granularity to map different event statuses to different workflows for evaluation. This allows clients to specify an event status to evaluate with a given workflow, rather than evaluating all event statuses by default. (E.g. Instead of evaluating attempts, successes, and failures, can have a workflow just evaluate attempts.)

In addition, clients can map an event status to no workflow at all and store the event data for internal analytics.

To access this feature, please reach out to your Alloy representative.

Clients now have the ability for a single Alloy entity to store and be referenced by multiple external entity IDs.

The most common scenario is when clients using Alloy for onboarding and ongoing monitoring create a unique identifier for an entity during onboarding, and later a separate identifier once the entity’s account is opened. To prevent duplicate entity creation and to preserve historical data, an entity can be referenced by any of their multiple unique identifiers.

Another use case is clients with multiple systems sending data to Alloy. Unique identifiers from those separate systems can be added to a single entity in Alloy.

Clients will be able to:

• Add multiple additional external entity IDs to entities
• Utilize the entities, evaluations, journeys, and events APIs using any of the entity's external entity IDs
• Search evaluations, entities, applications, alerts by any of the entity's external entity IDs
• Search any historical records by any of the entity's external entity IDs
• Merge entities and retain all external entity IDs.

Clients can now sandbox test Rule Based Notifications and be alerted for rules which have been hit in their production or sandbox environment. Rule Based Notifications allows you to set up alerts to be informed when pre-defined thresholds are breached, enabling proactive detection of anomalous activities that might indicate fraud.

Set up and configuration only takes a few steps – check out this guide for a few sample rules or learn more here in LAB.

Clients on Journeys can use the CLEAR SDK Plugin to seamlessly and securely verify users. CLEAR’s services allow users to create or leverage an existing CLEAR account to provide verified and secured identity information, which can be leveraged at the time of onboarding or as step-up verification on an ongoing basis.

Existing SDK clients can turn on the CLEAR SDK plugin in the SDK configuration modal. If you’d like to try the Alloy SDK, reach out to your CSM or [email protected] to learn more.

Clients on Journeys can use the LexisNexis ThreatMetrix SDK Plugin for capturing device signals and decisioning on them in Alloy.

To turn on the Threatmetrix SDK Plugin:

• Navigate over to your account Settings
• Click on “SDK” in the left white sidebar
• Click on the Journey you wish to configure it for
• In the box for “Device and Behavioral Risk Service Settings”, click on the pencil icon in the top right corner
• Click the toggle under Threatmetrix to enable the plugin.

For more information on implementing ThreatMetrix through the Alloy SDK, check out our developer documentation.

To purchase the LexisNexis ThreatMetrix data product, please speak with your Alloy representative. Alloy is a reseller of LexisNexis ThreatMetrix.

When end customers submit an application for a new digital banking product, clients will be able to deploy an interface to collect multiple documents as part of their application.

Applicants are shown a prompt with a list of documents they are required to upload. They can drag and drop multiple files into the interface, and scroll through the flow to upload different types of documents.

Collected documents will be stored on the entity’s record and available to review in the dashboard. They can be sent as an array to the client’s preferred vendor for processing.

The document collection landing page is fully customizable, including setting conditions for when to collect documents based on the applicant’s evaluation outcome. See documentation [link] for full details.

Clients using published attributes can now group related attributes for improved readability and a more seamless review experience. Published attributes are attributes associated with an entity that persist and can be used in any subsequent workflow for decisioning. Though published attributes are endlessly customizable, a few common attributes clients have set up include: customer income, employment status, risk score.

Appropriately permissioned agents can now create, edit and order category groupings for published attributes in Settings > Published Attributes. Published attributes that do not have a specified Grouping will be left in an uncategorized Grouping.