Skip to main content

Feature 419126: DocuTech Integration/Option 2 - Future State / Custom Docs

Ashley Bor
  • Updated

OVERVIEW

  • Provides ability for client to 
    • Request disclosures from IME
    • Request Mavent Compliance Check report from IME
    • Prevent user from ordering Disclosures if Compliance Check fails
    • Parse the esigning pushbacks in Encompass direct from DocuTech. 

 

Description

  1. Create Disclosure Tracking Encompass workflow to 
    1. Suppress full Disclosure Tracking exports to encompass
    2. Add Encompass Loan GUID to Disclosure Request payload
    3. Include additional data mappings for Borrowers in Encompass
  2. Create request and processing for Mavent compliance check product

 

Detailed Functionality

  1. Create new Partial Export to Encompass workflow for Disclosures Tracking.
    1. Export to Encompass for Disclosures Sent
    2. Suppress Export to Encompass for:
      1. Disclosures Received
      2. Disclosures Signed
    3. Suppress processing Individual Signed Disclosures - but only the full merged package.
    4. Suppress export of Signed merged Disclosure package.
    5. Add Encompass Loan GUID to  DocuTech Disclosure Request payload
    6. Include additional data mappings for export to Encompass
      1. CX.DOCUTECH.ORDERID1
      2. CX.DOCUTECH.PAIR1DTR1
      3. CX.DOCUTECH.PAIR2DTR1
      4. CX.DOCUTECH.PAIR3DTR1
      5. GSEVENDOR.X49#1
      6. GSEVENDOR.X50#1
      7. GSEVENDOR.X49#2
      8. GSEVENDOR.X50#2
      9. GSEVENDOR.X49#3
      10. GSEVENDOR.X50#3
  2. Mavent Compliance Check processing
    1. Mavent default hard stop (if configured) will trigger if any one or more of the following are failed.  
      1. Warning is not failure
    2. Test not run is not failure
    3. Tests reviewed
      1. ATR/QA 
      2. TILA/RESPA
      3. High Cost
      4. Higher Priced
      5. State Rules
      6. License
      7. NMLS 
      8. GSE 
      9. Enterprise Rules 
      10. HMDA 
      11. OFAC/SSN 
      12. Other 
    4. Response popup will provide confirmation of pass, or detail results if any failure is received
    5. Mavent report will be added to Doc Vault
    6. Audit log entry will be added for results

 

Configuration & Prerequisite Information

  1. The following new Configuration will be added to System Admin to determine Partial Export to Encompass workflow for Disclosures Tracking.
    1. Location: System Admin > Configuration > Configuration Environment
    2. Key Name: ExportToEncompass.DisclosureTrackingCustomDocutechService
    3. Default Value: false
    4. Tooltip: When set to True, Export to Encompass for Disclosure Tracking will use the rules for the Custom Docutech Service.
  2. The following new configuration will be added to Vendor Manager to create identification of specific Compliance Check vendor.
    1. Location: Vendor Manager > Product Settings
    2. Vendor = DocuTech 
    3. Product = Document Generation
    4. Config flag to indicate Compliance Check vendor
      1. Field Name: "Compliance Check product:"
        1. Options: 
          1. Interthinx
          2. Mavent

 

Acceptance Criteria

Full Set of Prerequisites.  Specifics needed for each Use Case are given below.

  1. Encompass Export to LOS
  2. Disclosures - DocuTech vendor
  3. Compliance Check Required to Create Initial Disclosures = Yes
  4. Show Compliance Check popup = Yes
  5. BRMS BA/ARCH task must be complete
  6. Vendor Manager > Vendor Product Settings > Compliance Check product must = Mavent
  7. SystemAdmin > Configurations > Environment > ExportToEncompass.DisclosureTrackingCustomDocutechService = "True"

 

Use Case # 1: Prerequisites (Client must be configured for)

  1. Encompass Export to LOS
  2. Disclosures - DocuTech vendor

Use Case # 1: Verify new configurations

  1. Access Loan Center > Vendor Manager
  2. Vendor = DocuTech
  3. Access Vendor Product Settings
  4. Verify new dropdown field exists: Compliance Check product
  5. Verify the default value shown is "Interthinx"
  6. Verify the alternate option is "Mavent"
  7. Verify Tooltip "Select the name of the Compliance Product to be passed to the vendor"
  8. Change value to Mavent and save
  9. Exit Vendor Manager
  10. Reaccess Vendor Manager > Product Settings for DocuTech
  11. Verify the Mavent value has been persisted.
  12. Access System Admin > Configurations > Environment
  13. Verify the new system admin key has been added
    1. Key Name: ExportToEncompass.DisclosureTrackingCustomDocutechService
    2. Value Data Type: Boolean
    3. Default Value: false
    4. Tooltip: When set to True, Export to Encompass for Disclosure Tracking will use the rules for the Custom Docutech Service.
  14. Access System Admin > Integrations and Vendors > Disclosures
  15. Verify the following settings appear lined up correctly:
    1. Compliance Check Required to Create Initial Disclosures?
    2. Show compliance check popup
    3. Loan No. Required to Create Initial Disclosures?
    4. Export to LOS to Create Initial Disclosures?
  16. Verify the Informative Text has been added to the right of the following:
    1. Compliance Check Required to Create Initial Disclosures?
      1. Text: Request Compliance Check inline with Disclosures, with hard stop.
    2. Show compliance check popup?
      1. Text: When Compliance Check inline with Disclosures, show popup on Pass

 

Use Case # 2: Prerequisite (Client must be configured for)

  1. Encompass Export to LOS
  2. Disclosures - DocuTech vendor
  3. Compliance Check Required to Create Initial Disclosures = Yes
  4. Show Compliance Check popup = Yes
  5. BRMS BA/ARCH task must be complete
  6. Vendor Manager > Vendor Product Settings > Compliance Check product must = Mavent
  7. SystemAdmin > Configurations > Environment > ExportToEncompass.DisclosureTrackingCustomDocutechService = "True"

Use Case # 2: Verify DocuTech Mappings

  1. Create new loan in Loan Center
  2. Complete the Application
  3. Shop for Rates and Apply a product
  4. Click to Create Initial Disclosures 
  5. Verify Compliance Check Requested popup displays
  6. Access Encompass and open the loan
  7. Obtain the Loan GUID from the loan properties
  8. Access CV Loan Center
  9. Access Integration Services
  10. Under the DocuTech vendor - Document Generation folder, Verify Compliance Check Request is created and sent to vendor
  11. Open the Compliance Check Vendor Request and verify the following
    1. New mapping exists: .../CX_LOS/PUSHBACK/@_OrderID
      1. Mapped value is "<Loan GUID from Encompass>_1"
    2. New mapping exists: //SMART_DOCUMENT/DATA/CUSTOM/CONFORMX/PREDATORY_LENDING/@PredatoryLendingVendor="Mavent"
    3. New mapping exists: 
      1. .../REQUEST_OPTIONS/DOCUMENT_FORMAT/@_Type = "PDF"
      2. .../REQUEST_OPTIONS/DOCUMENT_FORMAT/@_Type = "XML"
  12. Verify Compliance Check Response is received and posted to Doc Vault without error 

 

Use Case # 3: Prerequisites (Client must be configured for)

  1. Encompass Export to LOS
  2. Disclosures - DocuTech vendor
  3. Compliance Check Required to Create Initial Disclosures = Yes
  4. Show Compliance Check popup = Yes
  5. BRMS BA/ARCH task must be complete
  6. Vendor Manager > Vendor Product Settings > Compliance Check product must = Mavent

Use Case # 3: Mavent Compliance Check Request/Response Workflow

  1. Create new loan in Loan Center
  2. Complete the Application
  3. Shop for Rates and Apply a product
  4. Click to Create Initial Disclosures 
  5. Verify Compliance Check Requested popup displays
  6. Wait for Compliance Check Results popup
  7. Verify Results =
    1. Pass
      1. Verify the Compliance check Pass popup displays
      2. Click Continue to request disclosures
      3. Access Integration Services
      4. Open the Compliance Check Results pushback
        1. Extract the xml from the pushback xml and decode it.
        2. Replace the &lt and &gt tags to reformat the xml to be readable
        3. Review the data provided in the ServiceResponse/BaseReviewerStatus/Reviewer object to ensure it matches what is shown in the screenshot of the popup.
          1. @Status attribute contains the pass/fail value for each rule.
          2. Only rules with @applicable = "Y" should be processed and show in the popup.
          3.  
      5. Verify NO rule has a "FAIL" value (otherwise the Compliance Check should have failed).
        1. Note that this would be a Rule Failure for BA/ARCH to correct.
    2. Fail
      1. Verify the Compliance check Failed popup displays
      2. Take a screenshot of the popup
      3. Access Integration Services
      4. Open the Compliance Check Results pushback
        1. Extract the xml from the pushback xml and decode it.
        2. Replace the &lt and &gt tags to reformat the xml to be readable
        3. Review the data provided in the ServiceResponse/BaseReviewerStatus/Reviewer object to ensure it matches what is shown in the screenshot of the popup.
          1. @Status attribute contains the pass/fail value for each rule.
          2. Only rules with @applicable = "Y" should be processed and show in the popup.
      5. Verify the results for each individual test is displayed correctly in the popup 
      6. Verify at least one of the rules has a "FAIL" value (otherwise the Compliance Check should have passed).
        1. Note that this would be a Rule Failure for BA/ARCH to correct.
  8. Access Integration Services
  9. Verify the BRMS request and response xmls are posted
  10. Access Doc Vault
  11. Verify the Compliance Check report is posted in the Compliance folder
  12. Access Audit Log
  13. Verify the Compliance Check Requested and Compliance Check Pass/Fail entries are logged.

 

Use Cases # 4: Prerequisites (Client must be configured for)

  1. Encompass Export to LOS
  2. Disclosures - DocuTech vendor
  3. SystemAdmin > Configurations > Environment > ExportToEncompass.DisclosureTrackingCustomDocutechService = "True"

Use Case # 4: Disclosures Processing - Single Borrower

  1. Create new loan in Loan Center with a single borrower
  2. Send a SecureLink to the Borrower to complete the Application
  3. As a Borrower, use the Securelink to login and Complete the Application
  4. As an LO, Refresh your loan
  5. Shop for Rates and Apply a product
  6. Click to Create Initial Disclosures 
  7. Once Disclosures are returned, Send SecureLink to Borrower
  8. Verify the Disclosure Status is updated to "Waiting for Signature"
  9. As Borrower, Use SecureLink to login and esign documents
  10. As LO, Refresh your loan
  11. Verify Disclosure Status = Disclosures Signed
  12. Verify the Merged Signed document is found in the Disclosure Package - Signed folder
  13. Verify this document is NOT exported to LOS
  14. Verify there is no Individual Disclosures - Signed folder
  15. Note: The file for this use case will be used in the following use case for Export to Encompass

 

Use Cases # 5: Prerequisites (Client must be configured for)

  1. Encompass Export to LOS
  2. Disclosures - DocuTech vendor
  3. SystemAdmin > Configurations > Environment > ExportToEncompass.DisclosureTrackingCustomDocutechService = "True"

Use Case # 5: Disclosures Processing - Single Borrower - Export to Encompass

  1. Continuing with the file from Use Case: Disclosures Processing - Single Borrower above...
  2. Open the file in Encompass
  3. Navigate to the form with the Custom Fields referenced in the requirements
    1. In CV's instance of Encompass, these fields are on the CV Test AP form
  4. VERIFY: The following fields have been populated correctly (as indicated in the requirements)
    1. CX.DOCUTECH.ORDERID1 = {encompassLoanGuid}_1
    2. CX.DOCUTECH.PAIR1DTR1 = {emcompassDtrBorrowerPairGuid_1003#1}
    3. GSEVENDOR.X49 = {cvBorrowerGuid_1003#1}
  5. VERIFY: No other fields have been populated

 

 

 

Related articles

Comments

0 comments

Please sign in to leave a comment.