Business Workflows Processor
The Business Workflows Processor uses rules-driven business transitions between statuses to help a bank see the status of an application. It renders the status of a record, i.e. in this case the loan application, in the workflow and provides processing that must occur for the application to move to the next step in its life cycle. For the Mobile Retail Onboarding, there is an end-to-end self-service flow.
The statuses can be used as input to generate reports and see the number of successful applications or to see the status of each customer.
These are the following configurations:
The name is FTOS_BARET_MobileOnboarding attached to the entity FTOS_BARET_AccountApplication.
To download the diagram, click here.
Here is a list with the statuses and a definition for what it marks:
| Status name | Description |
|---|---|
| New | The status after the customer clicks on I want to open a account in Welcome screens. |
| Contact ans consents collected | The status after the customer inserts the email and phone number, agrees with the consents and swipes to the next page. |
| Validation email sent | The status after the email is sent. |
| Validation email failed to send | The status that marks if the servers fails to send the validation email. |
| Email validated | The status after the customer validates the email address. |
| Phone validated | The status after the customer validates the phone number. |
| Phone validation failed | The status when the customer has inserted more than five times the code and failed the validation. |
| Financial info collected | The status after the customer completes Tell us a few things about you and swipes to the next page. |
| PEP triggered | The status when the customer selects that they are as a Politically Exposed Person. |
| Package selected DC | The status when the customer selected a package containing a physical debit card. |
| Package selected no DC | The status when the customer selected a package without a physical debit card. |
| Card customized | The status when the customer chooses a color for the card and swipes to the next step. |
| Card delivery method set | The status after the customer selects the delivery method and swipes to the next step. |
| OCR launched | The status after the user selects the OCR method. |
| OCR passed | The status after the OCR automation processor performs the scanning successfully. |
| OCR failed | The status after the customer failed to scan the document more than five times. |
| Liveness launched | The status after the customer swipes to take a selfie. |
| Liveness postponed by user | The status when the customer clicks I'll do it later in the step Selfie. |
| Liveness passed | The status after the selfie is performed successfully. |
| Liveness failed | The status after the selfie fails to pass five times. |
| Personal data submitted | The status after the customer confirms and inputs the details needed on the personal data page. |
| Contracts generated and sent | After the user confirms the personal details and swipes to the next step. |
| Contracts not generated | The status when there is an error in the documents generation process. |
| Contract not sent | The status when there is an error and the email with the contract was not sent. |
| Contract Signed | The status after the customer signs the contract using One-Time-Password. |
| Expired | The status when an application has been left opened for 24 hours. |
For more details, see Business Workflow.