Our new Policy Library feature lets you create, save, and reuse your own snippets, or modular blocks of workflow logic. A new tab offers an account-specific repository for custom decisioning snippets, making it easy to standardize logic, modularize workflows, and build faster as your policies evolve.

With this feature, you can:

• Create and reuse your own policy snippets: Save commonly used logic once and reuse it across workflows within your account (the ability to publish snippets is configurable by role permission).
• Standardize decisioning internally: Ensure teams are building from the same trusted logic, reducing inconsistencies and rework.
• Browse and search with ease: Quickly find snippets by name or use case directly from the Alloy workflow editor.
• Deploy with confidence: Similar to Alloy-created snippets, you can insert snippets into workflows with guided merge logic and preview before setting live.

With Alloy’s ongoing investment in self-service capabilities, the Policy Library offers a single place to access both Alloy-recommended logic and your organization’s defined policies. 

You can find more details in this help article. 

We’ve improved the evaluation review experience by automatically hiding cards that don’t contain any data. This keeps Evaluations focused on meaningful results and makes them easier to review at a glance.

Some cards will continue to appear even when no data is returned, as they provide important context or configuration access. For a full breakdown of which cards are always shown versus conditionally hidden, please refer to our documentation.

View more context on an Evaluation in a new expansion on Rule Explainability with the Workflow Navigator. Users now have the ability to navigate the Workflow in a read-only view and see the Tags, Outcomes, and Rules that have been set for the Evaluation. Through the Navigator, users see context on Services, Inputs, Outputs, Published Attributes, and Matrix Models to help them better understand the Evaluation Rules and Outcomes.

With this release, users are able to:

• Understand the dependencies between Tags, Services, Published Attributes, and other configuration components for a given Evaluation
• View the Workflow outputs that have been set or not set based on the logic
• More effectively troubleshoot an Evaluation by traversing the Workflow and identifying the thresholds that were triggered
• Gain insights into areas of their policies that could be optimized or improved with additional Tags or logic

Alloy now supports custom Outcomes in Workflows and Journeys, which gives users the ability to tailor Outcome names, colors, and icons to better align to your organization’s risk review protocols and provide the right context for Evaluations, Applications, Alerts and Investigations. In addition, you can now add a characteristic to your Outcome letting Alloy know if the Outcome was good, bad, or neutral.

Here's what you should know:

• Any existing or new custom Outcomes can be tailored in Settings
• Preview how the customized Outcome will appear throughout the platform during creation
• View the Workflows and Journeys where an Outcome is actively being used in our enhanced Outcome Settings Page

Clients can now view all entities that were evaluated, were processed through a portfolio evaluation, or were not evaluated but may have been passed on through the Events API or legacy Entities API (for example: if the entity was onboarded outside of your Alloy instance and/or there has been no associated activity that has since triggered an alert, that entity would be considered ‘unevaluated’). Previously, the Entities page only displayed entities that had undergone a real-time evaluation.

Additionally, for clients using portfolio workflows, the Entity Detail page now displays a list of portfolio evaluations that the entity has been shortlisted in. These updates enable Alloy to serve as the single source of truth, providing teams with complete visibility into all the entities in their portfolio and allows them to take action on these entities in the future (e.g. create an investigation on that entity).

Clients now have the ability to link separate transactions using a unique identifier. Common examples of disparate but related transactions that clients may want to link include chargebacks, refunds, and disputes.

This can be used by any client utilizing Alloy for transaction monitoring via the Events API.

With this dedicated field in the Alloy platform, we will be able to build more functionality on top of this unique identifier related to alerts and decisioning capabilities.

To set up transaction linking, please reference our API documentation.

US clients using the AI-powered Fraud Attack Radar (FAR) can now benefit from more improvements to the FAR dashboard and will better allow them to autonomously and quickly triage following a suspected fraud attack. Clients will now be able to:

• View a summary of all attacks for the filtered time period
• View the top 4 indicators for an attack in the collapsible drown down
• Mark the status of an attack using the following options: Under Review, Confirmed Attack, Not Fraud Attack

To set up Fraud Attack Radar, navigate to the Workflows page and click the ellipses menu for your chosen workflow. Select ‘Fraud Attack Radar’ to open up the set up configuration. Please note: the model requires a minimum of 2 months of historical data to accurately work and will take roughly 2 weeks to train. The model can only be configured for person-type workflows and may not yield the best results for low volume use cases.

PATCH Application Enhancement

AFEF clients can now update completed or in-flight Applications with the parent slug, giving users the ability to update parent associations at any stage in the applications process via the Applications Endpoint.  Parent auditor accounts are only able to view records assigned to them. To set this up, please reach out to your Alloy representative with any questions.

AFEF Entity Endpoint Enhancement

AFEF clients can confirm their parent mappings via the entity endpoint.  This enhancement gives clients the ability to ensure their mappings are correct in a quick and scalable way. Users can call the entity endpoint and retrieve the parent mapping in the header. To set this up, please reach out to your Alloy representative with any questions.