Mortgage Loan approval workflow at run-time

1. Mortgage Loan approval workflow at run-time

2. Mortgage Loan Application Approval Process Bank Borrower Reviewer Approver Sample Loan application approval workflow design

3. Step 1a: Applicant fills up a form. Most of the fields are dynamically populated based on what user enters in certain fields. User enters Borrower Account Number and all the rest of the fields get auto-filled.

4. Step 1b: Rest of the Form fields are auto-filled based on Borrower Account number. User enters Borrower Account Number and all the rest of the fields are auto-filled.

5. Step 1c: Submitting a Form triggers a application approval workflow in the Bank. Submitting the Form triggers a workflow that routes the form as workflow tasks to various Business end-users for review and approval. Here a Bank employee’s ‘Task Manager’ shows a new task assigned for approval.

6. Step 2: Bank employees responsible for review and approval of a Loan application access their workflow tasks through secure login and perform necessary actions on the loan applications. Users respond to their assigned task by opening the task and start to work on it. They can attach documents. After the work is Completed, user clicks on Finish Task. After finishing the task the workflow proceeds to the next step in the Process. Refer to the workflow Design sample shown in the later section of this document.

7. Solution Setup

8. Step 1a: Let’s first begin by designing and Web Form that is exposed to the Borrowers for filing a new Loan application. This Form appears under My Solutions and is a stand-alone form that is bound to a workflow. When creating this form make sure that the workflow theme is not selected. This Form triggers the Mortgage Review workflow.

9. Step 1b: Using the rich form option use the Palette to drag the Form components into the Form canvas.

10. Step 1c: Click on Rules to configure a rule that will dynamically call a web service to pull in data values to automatically auto-fill some of the Form fields at Run-time. Click on the attached document to see the syntax. This rule makes a call to a rest Web Service which is executed in Adeptia. This web service extracts the data needed to auto-fill the form fields based on a value entered in one of the field. Later in this document there is description on how to publish rest web service in Adeptia.

11. Step 2: Reuse the stand-alone form for Workflow tasks. Make 2 copies of the form and then attach them when configuring the workflow tasks. Reusing the same form will keep the look and feel of the forms consistent throughout the workflow. Create 2 copies of the original form and add the fields related to Supervisor and Manager review and associate these forms to the workflow tasks below. Make sure you use the ‘workflow theme’ when creating the copies from the stand-alone form.

12. Step 3: Sample process design of the approval workflow. Workflow tasks Here is a sample workflow design that routes the form to supervisor for initial review and after the review decision is done then the workflow routes the form to Manager for final approval. This workflow is selected when the Stand-alone form is activated. Decision rule is: If ReviewerDecision = Yes then proceed to Manager Approval task else take another route. Here the ‘else’ route step is a placeholder.

13. Step 4: Sample process design to be published as a restFUL web service. Mapping has lookups to get data based on Borrower account number. Open the mapping In the Mapper interface to see the details. This is a custom plugin that has the following code: context.remove("Resource End Path"); restResponse is a JSON object that has the following Syntax. {“FormFieldName”:”ContextVariableName”} Context variable is defined in the mapping. Open the Process flow and see the contents of the put-context-var.

14. Step 5: Publish the process flow defined in the previous step as a restFUL web service as shown below.