Journey Applications appear in the Application Queue in the Alloy dashboard. A Journey Application provides a unified view of an application, including its entities, evaluations, documents, notes, and decisioning information.

A single Journey Application can include multiple entities, such as a business and its beneficial owners. Each entity is evaluated independently, while the overall application status is derived from the statuses of all entity applications.

The header displays general information about the Journey Application:

The three-dot ellipses menu (⋮) in the upper-right corner provides actions for the entire Journey Application:

Rerunning an application uses the original payload and creates a new Journey Application. The new application is not linked to the original application in Alloy.

Use the Assign menu to assign the Journey Application to an agent. An application must be assigned before the Review button for an evaluation becomes active.

The left side of the page lists the entities included in the Journey Application. Each entity panel includes:

The entity panel’s three-dot menu includes:

Each entity has its own Entity Application record and status. For multi-entity applications, the per-entity statuses are available in the entity_applications response data.

The right side of the page displays the evaluation for the currently selected entity.

The evaluation’s three-dot menu includes:

When an evaluation is rerun, Alloy creates a new evaluation with a unique evaluation token while retaining the association with the same entity. The rerun may use the same workflow or a different workflow and can include updated applicant data.

A rerun evaluation does not resume or change the original Journey Application. The new evaluation is for review purposes only, and its outcome does not affect the application.

Journey Applications are created through the Create Journey Application API. The request must include the entities to be processed. The same Create, Update, and Rerun endpoints support both single-entity and multi-entity applications.

When rerunning applications within 30 days, Alloy may return cached data-service responses. Use the alloy-refresh-cache header set to true when creating an application through the API to request new responses from data services.