Clients can now merge multiple entities into a single entity through our new dedicated API endpoint. For instance, if a client identifies a duplicate entity, they can resolve this by calling the new endpoint to merge the duplicate entries and retain a single Alloy entity ID. All associated information with the duplicate entity will be retained in the merged record and be available for future decisioning and reviews for that entity.

For more information on how to leverage the endpoint please reference our documentation: https://developer.alloy.com/public/reference/post_entities-merge

Ongoing Journeys and their manual review nodes will now have available outcomes of "Suspicious" and "Dismissed" rather than "Approved" and "Denied". These new outcome names reflect the riskiness of a post-origination event, compared to the prior origination-centric language.

Any client using Journeys and the Ongoing product can begin utilizing these “Suspicious” and “Dismissed” outcomes in new Journeys and to modify outcomes for existing Ongoing Journeys.

These new outcomes are visible during Journey building and in the Review Queue. (Please note these new outcomes are not yet captured in analytics.)

The Identity Element Velocity (IEV) is an Alloy service used in workflows. It is intended to count the number of entities (or evaluations with distinct SSN’s) with a matching subset of PII elements that run through a client’s Alloy account. The goal of this rule is to catch potentially suspicious entities sharing the same PII combinations due to identity theft or fraud.

Some clients may have different workflows set up for different lines of business that are managed by distinct third-party account opening systems. These clients will want to ensure that when a single entity applies for multiple products, the entity is not mistakenly recounted by the IEV rule across workflows as multiple distinct entities.

Previously, the only option for the scope of the IEV count was across all workflows in an account. To address this, when editing a workflow, clients now have the option to scope the IEV count of entities with a matching subset of selected PII elements for a specific workflow. With this scope, an entity is counted in the velocity count if it’s at least been run through the current workflow, even if it has also been run through other workflows as well.

All clients will now be able to click into any tags presented on review pages (such as the Evaluations, Application Review, and Transaction Evaluation pages) to see the associated rule logic. By having insight into the specific rule logic that triggered action on the entity, your agents can benefit from a more transparent, contextualized and efficient review.

Ongoing Monitoring clients will see updates to the Transactions Evaluation page which will provide them with more visibility into transaction-level data to better enable them to navigate and manage reviews more efficiently. To navigate to this page from Case Management, click on the Evaluations icon under the ‘Tags Triggered’ panel to view more details.

Changes include:

• Detailed transaction summary: access more granular, contextual information based on the payment type, allowing for a deeper understanding of each transaction’s context and history.
• Overview of the transaction path: illustrates the status of the payment and how the funds have moved from the source account to the counterparty account.
• Counterparty matches: if you are also utilizing Alloy for counterparty screening, you’ll also be able to view potential watchlist matches related to that transaction and optionally be able to take action on it (i.e. dismiss/suppress or escalate).

Clients on Journeys will see an update in how manual review nodes are surfaced in the Journey Application page, to provide better visibility where multiple rounds of review are required.

For any new or existing Journeys built using manual review nodes, the stepper component on the Application review page will display all manual reviews as separate nodes. All review notes will be visible within the individual manual review nodes.

New levels of permissions and built-in validations are available to set guidelines around how your team interacts with Published Attributes in the Alloy platform. This ensures that only the appropriate Published Attributes can be edited by an agent, and also ensures that certain Published Attributes can be updated only to a value that makes sense.

Admin users are able to set permissions and configurations for editing and updating Published Attributes. Admins are able to:

• Select which Published Attributes can be updated by agents in the dashboard
• Set parameters for the set or range of values that can be accepted in a given Published Attribute

All relevant API endpoints have been updated to ensure that “configurable by agents” and “acceptable values” can be set or updated via API as well as via the dashboard.

In addition, built-in validations will display error messages when:

• An admin attempts to set default values and optional acceptable values that conflict with each other
• An agent attempts to make an invalid update on a Published Attribute on an entity, i.e. an update that falls outside of the set parameters of the Published Attribute

Clients on Journeys will be able to view and search Applications by an External Application ID, a new, reusable external identifier. This identifier can stand for an Application or multiple Applications that are linked within a client’s account, and it can be associated with any number of Journey Applications within Alloy.

Alloy users will be able to search the Application queue by this external application ID to find all associated Journey Applications in Alloy.

In addition, external_application_id is available via the API as:

1. An optional request body parameter to existing Journey Applications.
   1. See API documentation:
      1. Create Journey Application
      2. Re-Run Journey Application
2. As separate Journeys endpoints for clients who would prefer to not have to reference Alloy’s Journey Application tokens.
   1. See API documentation:
      1. Get Latest Journey Application by External Application ID
      2. Update Latest Journey Application by External Application ID
      3. Re-Run Latest Journey Application by External Application ID