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
- Create Disclosure Tracking Encompass workflow to
- Suppress full Disclosure Tracking exports to encompass
- Add Encompass Loan GUID to Disclosure Request payload
- Include additional data mappings for Borrowers in Encompass
- Create request and processing for Mavent compliance check product
Detailed Functionality
- Create new Partial Export to Encompass workflow for Disclosures Tracking.
- Export to Encompass for Disclosures Sent
- Suppress Export to Encompass for:
- Disclosures Received
- Disclosures Signed
- Suppress processing Individual Signed Disclosures - but only the full merged package.
- Suppress export of Signed merged Disclosure package.
- Add Encompass Loan GUID to DocuTech Disclosure Request payload
- Include additional data mappings for export to Encompass
- CX.DOCUTECH.ORDERID1
- CX.DOCUTECH.PAIR1DTR1
- CX.DOCUTECH.PAIR2DTR1
- CX.DOCUTECH.PAIR3DTR1
- GSEVENDOR.X49#1
- GSEVENDOR.X50#1
- GSEVENDOR.X49#2
- GSEVENDOR.X50#2
- GSEVENDOR.X49#3
- GSEVENDOR.X50#3
- Mavent Compliance Check processing
- Mavent default hard stop (if configured) will trigger if any one or more of the following are failed.
- Warning is not failure
- Test not run is not failure
- Tests reviewed
- ATR/QA
- TILA/RESPA
- High Cost
- Higher Priced
- State Rules
- License
- NMLS
- GSE
- Enterprise Rules
- HMDA
- OFAC/SSN
- Other
- Response popup will provide confirmation of pass, or detail results if any failure is received
- Mavent report will be added to Doc Vault
- Audit log entry will be added for results
- Mavent default hard stop (if configured) will trigger if any one or more of the following are failed.
Configuration & Prerequisite Information
- The following new Configuration will be added to System Admin to determine Partial Export to Encompass workflow for Disclosures Tracking.
- Location: System Admin > Configuration > Configuration Environment
- Key Name: ExportToEncompass.DisclosureTrackingCustomDocutechService
- Default Value: false
- Tooltip: When set to True, Export to Encompass for Disclosure Tracking will use the rules for the Custom Docutech Service.
- The following new configuration will be added to Vendor Manager to create identification of specific Compliance Check vendor.
- Location: Vendor Manager > Product Settings
- Vendor = DocuTech
- Product = Document Generation
- Config flag to indicate Compliance Check vendor
- Field Name: "Compliance Check product:"
- Options:
- Interthinx
- Mavent
- Options:
- Field Name: "Compliance Check product:"
Acceptance Criteria
Full Set of Prerequisites. Specifics needed for each Use Case are given below.
- Encompass Export to LOS
- Disclosures - DocuTech vendor
- Compliance Check Required to Create Initial Disclosures = Yes
- Show Compliance Check popup = Yes
- BRMS BA/ARCH task must be complete
- Vendor Manager > Vendor Product Settings > Compliance Check product must = Mavent
- SystemAdmin > Configurations > Environment > ExportToEncompass.DisclosureTrackingCustomDocutechService = "True"
Use Case # 1: Prerequisites (Client must be configured for)
- Encompass Export to LOS
- Disclosures - DocuTech vendor
Use Case # 1: Verify new configurations
- Access Loan Center > Vendor Manager
- Vendor = DocuTech
- Access Vendor Product Settings
- Verify new dropdown field exists: Compliance Check product
- Verify the default value shown is "Interthinx"
- Verify the alternate option is "Mavent"
- Verify Tooltip "Select the name of the Compliance Product to be passed to the vendor"
- Change value to Mavent and save
- Exit Vendor Manager
- Reaccess Vendor Manager > Product Settings for DocuTech
- Verify the Mavent value has been persisted.
- Access System Admin > Configurations > Environment
- Verify the new system admin key has been added
- Key Name: ExportToEncompass.DisclosureTrackingCustomDocutechService
- Value Data Type: Boolean
- Default Value: false
- Tooltip: When set to True, Export to Encompass for Disclosure Tracking will use the rules for the Custom Docutech Service.
- Access System Admin > Integrations and Vendors > Disclosures
- Verify the following settings appear lined up correctly:
- Compliance Check Required to Create Initial Disclosures?
- Show compliance check popup
- Loan No. Required to Create Initial Disclosures?
- Export to LOS to Create Initial Disclosures?
- Verify the Informative Text has been added to the right of the following:
- Compliance Check Required to Create Initial Disclosures?
- Text: Request Compliance Check inline with Disclosures, with hard stop.
- Show compliance check popup?
- Text: When Compliance Check inline with Disclosures, show popup on Pass
- Compliance Check Required to Create Initial Disclosures?
Use Case # 2: Prerequisite (Client must be configured for)
- Encompass Export to LOS
- Disclosures - DocuTech vendor
- Compliance Check Required to Create Initial Disclosures = Yes
- Show Compliance Check popup = Yes
- BRMS BA/ARCH task must be complete
- Vendor Manager > Vendor Product Settings > Compliance Check product must = Mavent
- SystemAdmin > Configurations > Environment > ExportToEncompass.DisclosureTrackingCustomDocutechService = "True"
Use Case # 2: Verify DocuTech Mappings
- Create new loan in Loan Center
- Complete the Application
- Shop for Rates and Apply a product
- Click to Create Initial Disclosures
- Verify Compliance Check Requested popup displays
- Access Encompass and open the loan
- Obtain the Loan GUID from the loan properties
- Access CV Loan Center
- Access Integration Services
- Under the DocuTech vendor - Document Generation folder, Verify Compliance Check Request is created and sent to vendor
- Open the Compliance Check Vendor Request and verify the following
- New mapping exists: .../CX_LOS/PUSHBACK/@_OrderID
- Mapped value is "<Loan GUID from Encompass>_1"
- New mapping exists: //SMART_DOCUMENT/DATA/CUSTOM/CONFORMX/PREDATORY_LENDING/@PredatoryLendingVendor="Mavent"
- New mapping exists:
- .../REQUEST_OPTIONS/DOCUMENT_FORMAT/@_Type = "PDF"
- .../REQUEST_OPTIONS/DOCUMENT_FORMAT/@_Type = "XML"
- New mapping exists: .../CX_LOS/PUSHBACK/@_OrderID
- Verify Compliance Check Response is received and posted to Doc Vault without error
Use Case # 3: Prerequisites (Client must be configured for)
- Encompass Export to LOS
- Disclosures - DocuTech vendor
- Compliance Check Required to Create Initial Disclosures = Yes
- Show Compliance Check popup = Yes
- BRMS BA/ARCH task must be complete
- Vendor Manager > Vendor Product Settings > Compliance Check product must = Mavent
Use Case # 3: Mavent Compliance Check Request/Response Workflow
- Create new loan in Loan Center
- Complete the Application
- Shop for Rates and Apply a product
- Click to Create Initial Disclosures
- Verify Compliance Check Requested popup displays
- Wait for Compliance Check Results popup
- Verify Results =
- Pass
- Verify the Compliance check Pass popup displays
- Click Continue to request disclosures
- Access Integration Services
- Open the Compliance Check Results pushback
- Extract the xml from the pushback xml and decode it.
- Replace the < and > tags to reformat the xml to be readable
- Review the data provided in the ServiceResponse/BaseReviewerStatus/Reviewer object to ensure it matches what is shown in the screenshot of the popup.
- @Status attribute contains the pass/fail value for each rule.
- Only rules with @applicable = "Y" should be processed and show in the popup.
- Verify NO rule has a "FAIL" value (otherwise the Compliance Check should have failed).
-
- Note that this would be a Rule Failure for BA/ARCH to correct.
- Fail
- Verify the Compliance check Failed popup displays
- Take a screenshot of the popup
- Access Integration Services
- Open the Compliance Check Results pushback
- Extract the xml from the pushback xml and decode it.
- Replace the < and > tags to reformat the xml to be readable
- Review the data provided in the ServiceResponse/BaseReviewerStatus/Reviewer object to ensure it matches what is shown in the screenshot of the popup.
- @Status attribute contains the pass/fail value for each rule.
- Only rules with @applicable = "Y" should be processed and show in the popup.
- Verify the results for each individual test is displayed correctly in the popup
- Verify at least one of the rules has a "FAIL" value (otherwise the Compliance Check should have passed).
- Note that this would be a Rule Failure for BA/ARCH to correct.
- Pass
- Access Integration Services
- Verify the BRMS request and response xmls are posted
- Access Doc Vault
- Verify the Compliance Check report is posted in the Compliance folder
- Access Audit Log
- Verify the Compliance Check Requested and Compliance Check Pass/Fail entries are logged.
Use Cases # 4: Prerequisites (Client must be configured for)
- Encompass Export to LOS
- Disclosures - DocuTech vendor
- SystemAdmin > Configurations > Environment > ExportToEncompass.DisclosureTrackingCustomDocutechService = "True"
Use Case # 4: Disclosures Processing - Single Borrower
- Create new loan in Loan Center with a single borrower
- Send a SecureLink to the Borrower to complete the Application
- As a Borrower, use the Securelink to login and Complete the Application
- As an LO, Refresh your loan
- Shop for Rates and Apply a product
- Click to Create Initial Disclosures
- Once Disclosures are returned, Send SecureLink to Borrower
- Verify the Disclosure Status is updated to "Waiting for Signature"
- As Borrower, Use SecureLink to login and esign documents
- As LO, Refresh your loan
- Verify Disclosure Status = Disclosures Signed
- Verify the Merged Signed document is found in the Disclosure Package - Signed folder
- Verify this document is NOT exported to LOS
- Verify there is no Individual Disclosures - Signed folder
- 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)
- Encompass Export to LOS
- Disclosures - DocuTech vendor
- SystemAdmin > Configurations > Environment > ExportToEncompass.DisclosureTrackingCustomDocutechService = "True"
Use Case # 5: Disclosures Processing - Single Borrower - Export to Encompass
- Continuing with the file from Use Case: Disclosures Processing - Single Borrower above...
- Open the file in Encompass
- Navigate to the form with the Custom Fields referenced in the requirements
- In CV's instance of Encompass, these fields are on the CV Test AP form
- VERIFY: The following fields have been populated correctly (as indicated in the requirements)
- CX.DOCUTECH.ORDERID1 = {encompassLoanGuid}_1
- CX.DOCUTECH.PAIR1DTR1 = {emcompassDtrBorrowerPairGuid_1003#1}
- GSEVENDOR.X49 = {cvBorrowerGuid_1003#1}
- VERIFY: No other fields have been populated
Comments
0 comments
Please sign in to leave a comment.