The sub-status setup page allows you to configure the sub-statuses you want to be a part of your application workflows.
The Setup page allows you to set, among other things:
name and description
what the status triggers
who is alerted that the application has got to that status
what assessment processes must be completed to move from the status
This article takes you through all the Setup page controls and what they do.
Minimum Config: Add Name and Description for your sub-status
At the very least, you need to add a Name and Description for your sub-status. It may be that this is all you need to configure for the sub-status, if so click Save when complete:
Set as approved
This control is used to tell Omni to allow the "submit to Core Banking" button to be enabled when you have reached this Status.
This will mean that when you have got to Formal Approval Granted status, the final 'submit' button in Omni will be enabled:
Validate DLA
DLA is the "Designated Lending Authority". Users (usually assessors) will be given certain DLA Groups by their Lenders, and this will determine which applications types, and assessment activities, they are allowed to assess/complete on behalf of the lender.
The Validate DLA control will tell Omni to check the DLA Groups that the Lender has configured, and then determine if the current assessor is allowed to work on the application, now that it has got to a certain activity or type.
If an application gets to a certain sub-status, and Omni checks the DLAs for that User against the DLA rules for that channel and finds that the current User cannot complete the status, they will get an error telling them to assign the deal to a teammember that has sufficient DLA:
For more detail on configuring DLAs and this functionality, click here.
Milestone
When you set a sub-status to be a Milestone:
It will then appear on your timeline in the Omni Dashboard for your application record:
Trigger Assessment Process
This control will make the Assessment Module appear in Omni, when your application records gets to this sub-status:
⚠️ Note that this Control is an alternative way to enable the Assessment Module to the alternate trigger in the Journey Setup.
Use the Journey trigger if you are Ok with the Assessment Module appearing immediately in Omni.
Use this sub-status trigger if you want the Assessment Module to appear only when you get to a certain status.
The Assessment Module will run all business rules against your application data, and allow you to set conditions, build an assessment summary, and approve the application:
For full detail on the Assessment Module, click here.
Trigger unconditional approval process
When an application gets to a certain final status (eg formally approved), a lender might want Omni to trigger a set of automated checks or activities before moving on to the Settlement workflow. An example of this automated check is to Refresh the product (and rates, repayments etc) to check for any changes now that the application is formally approved:
For more detail on the Unconditional Approval Process, click here.
Alert the following management participants
A participant is anyone who works on an application - eg Broker, or Assessor. You Add the management participants in the Setup section of your Loanapp. A key participant will be the person submitting the application (the broker). But you may also want other parties to be added to an application (eg BDMs):
When you setup a sub-status, you can configure that sub-status to trigger an 'alert' (email) to the Participants that you list on that sub-status:
Generally, you will only want to set alerts to go to interested parties for the milestone-type sub-statuses.
To find out more about the content of the Alert message, click here.
Linking your Sub-status to a Process
For each sub-status that you create, you can set what "Process" is triggered when you enter, or exit, the status.
This is mostly used to link a Process on Entry - ie when you reach this sub-status, a new Process triggers.
An example of linking this status to a Process is where the status of LMI required will trigger the Process "LMI Premium and Quote":
The Process on exit functionality is less commonly used - but is useful where you might want to 'undo' a status.
eg Where the status on an application has reached Declined....however the applicant provides more detail which constitutes a re-assessment... in this circumstance, the Lender might set a Process on Exit, which will re-set the assessment.
Allocate co-ordinator
The Allocate co-ordinator flag will mean that when the sub-status triggers the new 'Process on entry' to be created, the team allocation logic will be checked so that the new Process will be auto-allocated to the correct team/person on a team.
🤹 Allocation logic is generally tied to/related to the DLA Logic set by a lender and then assigned to each Team-member.
In the above example: this might mean that if a target team has 4 members, but only one of those members can apply for LMI quotes - then this application would be allocated to that teammember at this status change.
BCM events that trigger this status
This setting is used where we have an integration with an external system that sends BackChannel Messages to our Omni workflow. Where this is the case, we can then link these BCMs to an application sub-status.
An example of this is where the Settlement Solicitors have received Instructions to prepare mortgage documents, and have sent a BCM to OMNI as there are outstanding documents that are needed for the settlement to proceed.
The BCM Event of "Loan Documents and Requirements Incomplete" will trigger the sub-status to change to "Docs Returned - Outstanding items".
Reviewing your list of sub-statuses
You can have a quick review of your sub-statuses by selecting the relevant Primary Status to get a list of sub-statuses within that Primary Status.
On this listing, you will be able to click through to edit (or delete) the sub-statuses; and also see some high-level detail without going into edit mode:
Sub-status title | This is important to be correct, as it will be displayed to your network when your application is in this status |
Icons | You are able to quickly see which of your sub-statuses have certain settings:  |
Description | Further detail describing the sub-status |
Process on Entry and Exit | Where you have set the sub-status to then trigger Action Processes, they will be listed here |