Clients on Journeys will experience a new versioning paradigm that brings enhanced flexibility and better visibility and audibility into logic changes within their Journeys. 

-The main change is the introduction of “Version pinning”, which ensures that a Journey version, once saved, is frozen in time with the workflow versions contained within it. Any subsequent logic changes in the new workflow version will result in a new Journey version to ensure those changes are captured in a more auditable way. (As a reminder, before this release, the active version of a Journey automatically used the active versions of the workflows contained within it, and workflow logic changes did not increment the Journey version.)

The key changes you’ll see in the dashboard are:

-When activating a workflow version (from either the workflow versions list or from the workflow builder itself), you'll now see an updated modal that lists all Journeys containing that workflow when activating a new workflow. This updated modal gives you more flexibility by allowing you to choose the appropriate action for each Journey, whether it's setting the new version as active, creating a draft version, or doing nothing (note that the default option will be different depending on whether errors would be introduced into the journey graph with the workflow change).

[Insert image #1 from release note]

-When swapping workflow versions in Draft Journeys, you’ll see that non-active versions are clearly highlighted with an orange outline, and an informational modal will alert you if a Journey is using non-active workflows. 

[insert images #2 and 3 from release note]

-Once you then go and try to set this Journey active, after activation, you will now see this new informational modal, alerting you that the journey is using non-active workflows. 

[insert image #4 from release note]

You can optionally go and set these workflows active if needed, but remember that the new paradigm does not require it. All that “active” means now is that it will become the “default” workflow version that would be added to a journey if you were to add the workflow from the “+” menu on the journey builder.

We’ve enhanced our auto-assign capability to give more granular permissions for a particular Role to only review entities that are in particular Review node type (e.g. a custom Review node, or a Manual Review node) to better accommodate different types of review processes and team structures.

This means that clients can now restrict certain (e.g. more junior) Role types to reviewing entities in only a subset of Review types, while more senior roles can float between queues and/or review JA as a whole.

To get started, navigate to Settings --> Roles and specify the Review node types (including the standard “Manual Review” node) for each of those Roles you set up. Multiple roles can have same Review node types selected. The default is “All Review nodes”.

Published attributes are attributes associated with an entity that persist and can be used in any subsequent workflow for decisioning. Published attributes provide a more holistic view of your customers by enabling you to track them throughout their whole lifecycle, utilizing insights from onboarding and beyond to feed into your ongoing decisioning.

Agents will also be able to view published attributes in the review experience to provide additional context and enable more informed decision making.

For more details and step-by-step instructions on how to test and use this feature, please refer to our technical documentation.

Clients will now see a side panel displaying a holistic view of an entity as part of their review experiences. This panel includes information about the entity’s PII, Published Attributes (if present), and Entity Fraud score (if present), helping to provide additional context for reviews.

To get started with this feature:

For evaluations or cases, click on the entity name box in the top left hand corner to summon the pane.

For applications or alerts, click the ellipses next to the entity name and select "View Entity Info". 

In order to view the regular entity page from alerts / applications, click "View Full Entity Profile" within the summoned entity pane.

Clients can now export a CSV report directly from the Review Queue for their reporting needs. This self-service option allows clients to access the data they need more efficiently.

To get started, navigate to the Review Queue page and apply any filters you’d like to help narrow down the data you’d like to export. Any filters that you apply on the Review Queue page will also be applied to the export. Click on the Export CSV button on the top right of the page to download the file. Please note that the maximum number of rows we support is 10,000.

Safely experiment with new risk strategies including new data sources* without adversely impacting your end users using Shadow Testing, our newest addition to the Testing Suite. This feature is available exclusively for clients on Journeys.

Shadow Testing allows you to make changes to your risk policy using production-level data against the policy which is already live - all in parallel and in real-time without impacting production decisioning. It eliminates performance issues and gives you an accurate view into the expected outcomes and impacts of varying risk strategies before deploying into production.

To get started, navigate to the Journey builder and click the ‘Test’ button on the top right to open up the Testing Suite. Select ‘Shadow Testing’ and configure the test to your specifications.

*Note that testing certain data services may incur charges. Please reach out to your Alloy representative prior to using Shadow Testing to test a new data service.

Clients on Journeys can now learn more about their Journey’s architecture with our interactive Journey Developer Guide and be equipped to autonomously integrate with Journeys and reduce potential errors.

With this new tool, you’ll be able to:

• see explanations for your Journey Architecture, including descriptions of each node, branch, and webhooks
• run a sandbox Journey Application step by step through each node in a Journey Branch
• see sample payloads
  • customize and validate the sample payloads
  • payloads can be copy and pasted into terminal to run, or be run directly via the Develop Guide panel.

To get started, navigate to your Journey’s Graph view, click the ellipses button on the top right, and select ‘Developer Guide’ to see the Developer Guide panel.

Ongoing Monitoring clients can now get real-time updates from Alloy on cases using case webhooks. These webhooks contain overview information about a case that can be triggered on case creation or case status updates. Please refer to our external docs for more information.