Reconciliation logic is needed for Journeys configured to evaluate joint applicants, businesses, or any other type of application which contains multiple entities. It is the high-level logic that determines the outcome of the application as a whole based upon the outcomes of each individual entity in the application. Only Journeys with single branches do not require this logic to be configured.

Application Outcome

See the screenshot below for an example of the original modal for configuring the Outcome Logic of a Journey when multiple branches and entities are included.

This modal can be accessed by clicking the Application Outcome button in the upper right corner of the Journey Editor. Note that this button will include a green check mark if this option is in use.

While this option is still available, there is a new, more robust method to configure this logic. This new method is detailed below in the Reconciliation section.

Reconciliation

The Reconciliation logic for a Journey Application with multiple entities and branches can now be configured as a workflow. This offers the ability to include tags, matrix models, output attributes, and anything else that can be configured in an Alloy workflow in your outcome logic. In general, this method brings the following benefits:

• The logic that dictates the final Journey Application outcome can now use a wide array of data points. This dramatically increases the flexibility and range of what is supported.
• Alloy can now support more use cases where clients need to be able to do some final logic or calculations across all of the entities in the application, and have those outputs be part of the final Journey Application outcome logic.
• Since the Reconciliation workflow supports custom JQ filters via Input Attributes, there is vast optionality with regards to what data clients can use in their outcome logic.

This functionality must be enabled in your account, so contact your CSM or support@alloy.com if you do not see the Reconciliation button in the Journey Editor. Once this button is activated and a Reconciliation workflow is configured, Alloy can disable the original Application Outcome button as it is no longer needed. Even if it is not disabled, if Reconciliation is set up with at least one outcome, Alloy will use that.

How to Configure a Reconciliation Workflow

1. Within the Journey Editor, click the Reconciliation button.
   1. 
2. Enter a name for the new workflow, then click Create.
3. A new browser tab will open with the Reconciliation workflow. Add anything to the workflow (for example, a placeholder Input Attribute), click Save, add any New Version Notes, click Save New Version, then return to the Journey Editor browser tab.
4. Save the Journey, then refresh your browser window.
5. Click the Reconciliation button again to access the workflow. Note that the Reconciliation button will now show a green check mark.
   1. 
6. In order to match the functionality of the original Application Outcome logic, create Input Attributes which check the outcome for each Entity Application. These will be used in the Reconciliation workflow’s outcome logic. For each Input Attribute, make sure to check the Parse with JQ checkbox.
   1. Here are a few example JQ filters that count the number of Entity Applications in the Journey Application and read the outcome for each EA. The payload structure is always the same for Reconciliation workflows, so these exact filters can be used. 
      1. Checks how many Entity Applications are included in the Journey Application:

         1. .entities | map(select(.data.imported.entity_application_outcome.outcome)) | length

      2. Checks how many Entity Applications got an outcome of “Approved”:

         1. .entities | map(select(.data.imported.entity_application_outcome.outcome == "Approved")) | length

      3. Checks how many Entity Applications got an outcome of “Denied”:

         1. .entities | map(select(.data.imported.entity_application_outcome.outcome == "Denied")) | length

   2. 
7. Once the Input Attributes have been created per the above screenshot, it is time to create the Reconciliation workflow tags.
8. Create an All Entities Approved tag:
   1. 
   2. Be sure to select this Input Attribute:

      1. .entities | map(select(.data.imported.entity_application_outcome.outcome == "Approved")) | length

      2. The dynamic Input: .|M|L checks if the total number of EAs in the JA equals the number of EA Approved outcomes.
9. Create an At Least 1 Entity Denied tag:
   1. 
   2. Be sure to select this Input Attribute:

      1. .entities | map(select(.data.imported.entity_application_outcome.outcome == "Denied")) | length

      2. This checks if the number of Denied EAs is greater than 0.
10. Create an Approve the App tag:
    1. 
    2. This tag is set if the All Entities Approved tag is set.
11. Create a Deny the App tag:
    1. 
    2. This tag is set if the At Least 1 Entity Denied tag is set.
12. Configure the Outcomes for the Reconciliation workflow:
    1. 
    2. If Deny the App is set, evaluations will be Denied.
    3. If Approve the App is set, evaluations will be Approved.
    4. Otherwise, evaluations will go to Manual Review.

While the example provided above is a basis on which you can build, you can add any other logic you want and include it in the Reconciliation workflow outcome logic.