Alloy now supports exporting a detailed timeline log of events for entities to enable clients using Onboarding and Credit Underwriting to more easily meet audit requests. This log will include events such as: entity details, any Journey applications and evaluations run on the entity, actions and decisions taken by agents, documents and notes uploaded on the entity, any published attributes being used by the entity and a history of changes on published attributes.

To get started, navigate to the Entities page and select the entity. From the vertical ellipses menu on the top right, click ‘Download Entity Timeline’, and you’ll be able to download a text file with a log of events.

If you’d like to use this feature, please reach out to your Alloy representative.

Clients are now able to export a CSV for a full history of Agent Actions. Previously, all data exports in the platform were limited to 10k rows.  

To get started, click on your user profile icon and select ‘Auditing’. This will bring you to the Agent Actions page where you can click on Export CSV. You'll get a notification under the bell icon and an email notification when the file is ready to be downloaded!

Please note: users must be appropriately permissioned (‘Agent can  view the Audit Actions page’ must be enabled).

System for Cross-domain Identity Management (SCIM) gives clients using SAML for SSO-based login the ability to provision Alloy users directly from their identity provider.

From their identity provider, clients will be able to 

• Grant users access to Alloy
• Remove users’ access to Alloy
• Assign users to roles/ groups in Alloy
• If they are deleted from the identity provider, they will be archived within Alloy 

When users are manually created within Alloy, these users will not be created within the identity provider automatically. However, new users can be linked within the identity provider.

To activate SCIM, clients can reach out to Alloy’s Support Team.

Clients on Journeys will see additional visual updates to the Versions List view for optimal usability:

• Versions are by default sorted in descending order. (Drafts no longer float to the top.)
• Sort by ascending or descending versions by clicking the arrow in the “Version” column.

When expanding details of a specific version:

• A "Dates Active" section shows all the times, and by whom, a given version has been set active. With this built-in audit trail, users no longer need to create a new Journey version every time someone sets an "inactive" version to "active".
• Outcomes used in the Journeys, along with the Services used, appear as well.

Clients using Published Attributes now have the ability to use a Published Attribute as both an Input and an Output attribute within a single workflow. This unlocks the ability to reference the present value of the attribute in order to set the new value of the attribute.

A Published Attribute can be used to dynamically calculate a customer’s compliance risk rating. The rating’s value will update by adding to or subtracting from a prior value in a workflow. By doing this, clients will be able to detect risk earlier than before and have a holistic view of the entity's risk that evolves over time.

An example for updating the String Risk Score on an entity:

To view the history of a Published Attribute’s previous values, click on the three dot menu in the entity panel, click “View Entity Info”, and hover over the clock icon to the right of the attribute’s name.

Clients using the credit panel will now see a broader set of credit report and tradeline data from the credit bureaus in the US, enabling them to conduct holistic and robust credit reviews. Previously, the credit panel only surfaced data from Experian.

The following data sources will now be surfaced in the credit panel:

Equifax

• Consumer credit data
• Business credit data
• Tradelines for Equifax consumer and business credit

Experian

• Tradelines for consumer credit (Experian consumer credit and Experian Netconnect)

Transunion

• Consumer credit
• Tradelines for consumer credit

View and Create Published Attributes Values in the Entity view

Clients using Published Attributes can now view and edit (which includes creating new values) Published Attributes values, allowing for more holistic and flexible decisioning. ‘Published Attributes are custom entity-level attributes that you can define and use in your decisioning throughout the customer lifecycle.

Published attributes can be viewed and edited directly in the Entity view or Entity Side Panel. You can view the most recent 5 values. Please note: in order to create a new Published Attributes value, users must be appropriately permissioned (Settings > Roles > Published Attributes)/

Clients can now share Entity Feedback Data with Alloy by marking entities as fraudulent directly in the Alloy dashboard. 

Entity Feedback Data for a customer account is your determination of whether an entity is fraudulent or not. Beyond the initial approve/deny decision, entity feedback data looks at behavior over time and shows both accounts that have been determined to be fraudulent, as well as accounts that have been approved, opened and are in good standing. Sharing Entity Feedback Data unlocks access to Alloy’s ML models, which are critical to a holistic identity-centric strategy. 

To get started, select ‘Send Entity Feedback’ from the vertical ellipses menu on the Entity page and a modal will appear where you can provide more details. Please note: this option will only appear to agents who have the permissions to submit Entity Feedback Data (to update permissions, navigate to Settings > Roles > Entity Feedback Data).

As a reminder, you can alternatively also submit Entity Feedback data through our dedicated API or upload a CSV file using our template via the Settings page in the Alloy dashboard.

A new banner will be displayed at the top of the Evaluation page in the case of a Partial error, to enable clients to better identify, understand and remediate errors. For Journeys clients, if this Evaluation is part of a Journey, it will be visible also from the Application view when the user clicks into the Evaluation.

This banner surfaces information that has been added to the raw response to help identify the blocking and blocked objects in there. The banner also includes a suggestion on how to resolve the partial, based on the exact cause.