/
Diagnosing nCino Auto Booking with FIS IBS Code Connect Problems With Glyue Run Histories

Diagnosing nCino Auto Booking with FIS IBS Code Connect Problems With Glyue Run Histories

Owned by Travis Walter
Last updated: Jun 01, 2023
10 min read

This document’s intended use is to allow you to diagnose and solve potential nCino issues on the fly.

A prerequisite for using this document is that you have access to Glyue and to the flow chart provided to you before production go-live. If you do not have access to Glyue or are missing the flow chart, please create a ticket on the Glyue Help Center for assistance.

When Should I Use This Page?

  • When you’ve attempted to book a loan through the automated booking tab and received an error message like this:

FAILED TO BOOK THE LOAN WITH THE SALESFORCE RECORD ID {Salesforce Record ID} TO THE CORE: [IBSDLB/V1]: {Error Message}

  • When you see a message like this and do not know why this issue occurred

  • When you see a message like this and don’t know where the field is in nCino that Sandbox Banking is using to map with

Already Know Where To Go?

Search through Sandbox Banking’s repository of Error Resolution pages to find a potential solution to your problem:
Note: If you don’t see one that matches then please open a ticket through your Glyue Help Center.

Paste Error Message Here

Not Sure Where To Go First?

Step 1 – Log Into Glyue

Step 2 – Navigate to the “Run History” Tab

Step 3 – Find the Most Recent Run History for the Loan in Question

It is recommended that you filter your run histories by, at the minimum, Start Date, to decrease the amount of time the text search takes. This is accomplished by selecting a Start Date from the left most field on the run histories page.

  • If you just booked the loan, this should be the first run history at the top of the scroll bar

  • If you are diagnosing an issue with a loan that was booked at an earlier time, please use the Text Search option on the right-hand side to search for the loan id in question.

    • The loan id (usually the field id or Record Id in nCino) is also present after LLC_BI__Loan__c/ in the loan’s URL in nCino, as seen in the example below:

    • If you can’t find the Text Search option, please create a support ticket

  • Please note that most integration runs that have issues will have a red [!] next to the integration name

    • If the details section of the Automated Booking Summary page in nCino has a message that says BOOKING FAILED -- RUN TIME ERROR ENCOUNTERED -- PLEASE REVIEW RUN HISTORY this means the loan booking failed due to a runtime error.

      • Sandbox Banking does not expect you to resolve runtime errors yourself. However, providing as much information to your engineer when opening a ticket is the best way to get the issue resolved quickly.

        • Runtime Errors manifest themselves in the Stack Trace of a run and may be accompanied by an empty Failure step in the run history. Follow Step 6 to retrieve the Stack Trace and place it in your request through the Glyue Help Center.

Step 4 – Select the Run History to Get More Information About the Booking

  • The integration name for the run that failed will be the wording next to the red [!] in the runs list

    • For example, in the image above, the integration name that failed was dlb_ncino_create_ibs_loan

Take note of the integration name for use in Step 7

Step 5 – Find the REQUEST Step(s) That Has the Red [!] Next to the Request

Please note, any REQUESTS that end in inq, for example cc_relationship_inq, may have failed, but are not the cause of your error.

REQUESTS that end in inq are used to inquire against the banking core for certain things. These things can be the account, note, commitment, etc. If they fail, this means that those things are not found on the core and are ready to be booked. If they pass, it can mean that portions of the integration gets skipped as the services don’t need to run.

Both a pass and a fail are handled by the integration and will not stop the integration from running.

REQUEST dlb_scp_loan is where the errors for Code Connect will primarily be.

  • Click on the REQUEST step(s) to open the Details page

Clicking on Failing REQUEST

  • Errors will be in the Response section on the Details page

Scrolling Down to Response Section and Seeing Error Message

Step 6 – Retrieve Error Message and Potential Cause from the REQUEST

Step 5 has prepared you to retrieve the necessary information to search for a solution.

Retrieving potential cause from the REQUEST:

Scrolling Down to the Response Section and Seeing Error Message

To find errors, scroll through or use the find feature (with ctrl + F) in the Response section until you find an error message that matches what was displayed in nCino.

  • Most of these messages are clear on what the issue is, but the Response section will show you which service request it falls under, which will help you in the next step if the message doesn’t have a clear solution for you.

Zoomed in View of Response Section With Below Field Highlighted in Blue

  • The cause of the issue will be in the Metadata field within the response of the REQUEST

    • MsgLst is the list of responses from Code Connect/Dynamic Loan Boarding

      • Text: Cause of the issue with the error message, process group, service name, unique id, and field

Using the cause and the field of the issue in your search in Step 8 can provide you with a useful and quick fix for your problem.

Most booking errors will be in the REQUEST dlb_scp_loan

  • Errors are produced in dlb_scp_loan but the real issue lies further up in the response payload

    • The error messages from Dynamic Loan Boarding will have a location and field of what is causing the issue, for example:

      • THE INDEX IS NOT YET SET UP|PG2|lnnwLoanNewNote|4|LNIndx - Pulled from above image’s response section

        • THE INDEX IS NOT YET SET UP - Error message

        • PG2 - Process group number, which can be found in the payload by doing a text search for the group number

        • lnnwLoanNewNote - Function Name of the service that failed, which can be found in the payload by doing a test search for the function name

        • 4 - Unique id of the function in the process group, which can be found in the payload by doing a text search for the unique id

        • LNIndx - The field that is causing the error in the service, which can be found in the payload by doing a text search for the field name

    • Using this, we can find the field(s) in the Request that is causing the issue:

However, failures can also be seen in service requests outside of dlb_scp_loan

  • An example of this would be retrieval or inquiry REQUESTS

Some errors will also include what is called a Stack Trace which provides the pure code response from the error. You do not need to analyze this section but should include it when you open a ticket for your SDE.

Stack Trace Example

  • To copy the Stack Trace for pasting into your new ticket, click the copy button:

    • This will grab all the information in the field and allow you to paste it anywhere you need it.

      • This button appears next to all the Details fields and has the same purpose.

Retrieving the original error message for your search in Step 8

  • Copying the entirety of the DETAILS section from the Automated Booking Summary page will be enough to use for your searching purposes in Step 8.

Step 7 – Find Where the Field is in nCino that Sandbox Banking is Mapping

With the retrieved Error Message, Integration, and Service Request from Steps 4, 5, and 6, you can easily find where this field lives in Glyue and what field Sandbox Banking is using for mapping.

Navigate to the “Build” Tab:

Build Tab

Navigate to the “Service Request” Component:

Service Request Component

Filter Service Requests by Integration Name:

Click on the FILTERS button:

Click on the Integration dropdown in the resulting Filters dialog and type in the name of the integration found in Step 4:

Click on the resulting integration option from the dropdown:

Click outside of the Filters dialog (into the grey area) to close the dialog:

Service Request listings have now been filtered by the integration that is failing.

Use the Find tool to Search for the Failed Service Request:

Search for lnnnwLoanNewNote Service Request

Access Field Mappings for the Service Request:

Right-click on the Service Request:

Click/Hover Go To/Go To (New Tab) at the bottom and select Field Mapping

Find the Field Where Failure Occurred and Review the Value Field:

Click the open button on the Value field:

The value Sandbox Banking is mapping lives here:

Other logic that corresponds to the field in question can be found on the same row. These include:

  • Potential Value Mapping Sets employed on the field

    • Value Mapping Sets translate the value sent in the field to another value, which is determined by the set.

  • Include If logic employed on the field

    • Include If logic is used by Sandbox Banking to include or not include a value when business logic dictates.

  • Include For Each logic employed on the field

    • Include For Each logic is used by Sandbox Banking to send the value in a loop depending on the logic within the field.

    • If you see fields duplicated in the request/response payload, this would be the place to look first!

To find the value mapping set for a field in question go to the Value Mapping Set column on the field:

Selected Value Mapping Set for LNIndx on lnnnwLoanNewNote

Right-click on the Value Mapping Set Field:

Click/Hover Go To at the bottom and select Value Mapping Set:

You may need to remove any text search to see a result

Right-click on the Value Mapping Set:

Click/Hover Go To at the bottom and select Value Mapping:

You may need to remove any text search to see a result

Results:

To find the Include If logic for a field in question go to the Include If column on the field:

Selected Include If for LNIndx on lnnnwLoanNewNote

Click the open button on the Include If field:

The logic Sandbox Banking is using lives here:

To find the Include For Each logic for a field in question go to the Include For Each column on the field:

Selected Include For Each Logic Block on PaymentScheduleLst Field

Click the open button on the Include For Each field:

The logic Sandbox Banking is using lives here:

If you have questions about how or why any logic is used in your integration, please open a ticket in your Glyue Help Center.

Step 8 - Find the Error Resolution Page For Your Error

Sandbox Banking has a repository of Error Resolution pages for your to search through so that you can either fix the issue yourself or provide more information to your SDE on opening a Glyue Help Center ticket for the issue.

By inserting the error message provided to you by Glyue in the search box below you will be presented with potential Error Resolution pages that match your specific error.

Note: If you don’t see one that matches then please open a ticket through your Glyue Help Center.

Paste Error Message Here

Related content