Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

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

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#DEEBFF

It is Sandbox Banking’s assumption 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?

...

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.

Live Search
external
spaceKeySIWPUB
sizelarge
additionalpage excerpt
placeholderPaste Error Message Here
labels

Table of Contents
minLevel2
maxLevel2

...

  • 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 Errorsmanifest themselves in the Stack Trace of a run and may be accompanied by an empty Failure step in the run history. Follow Step 6to retrieve the Stack Trace and place it in your request through the Glyue Help Center.

...

  • 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

Anchor
Step-5
Step-5

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.

...

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.

...

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.

...

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.

Anchor
Step-7
Step-7

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.

...

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/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:

...