Health Check

General information

Defined test cases

  1. Check Connectivity between MPO and nCino
    Test case name - nCinoConnectivity
    The nCino connectivity test makes a GET API call to check:

    • The refresh token has been created.
    • The nCino credentials are verified.
  2. Check Connectivity between MPO and Mambu
    Test case name - mambuConnectivity
    The Mambu connectivity test makes a GET API call to check the provided Mambu credentials and permissions.

  3. Check configured Deposit products in Mambu
    Test case name - mambuProducts
    The deposit products test uses the response from the previous connectivity test in Mambu to check that the same deposit products defined in the configuration also exist in Mambu.

  4. Check configured Deposit products in nCino
    Test case name - nCinoProducts
    The deposit products test uses the response from the previous connectivity test in nCino to check that the same deposit products defined in the configuration exist in nCino.

  5. Validate nCino endpoints
    Test case name - nCinoEndpoints.
    The validate nCino endpoints setting test makes a GET API call for each endpoint used in the connector to check that the nCino package in Salesforce is properly installed.

  6. Check Refresh Token
    Test case name - nCinoRefreshToken.
    The Refresh Token test compares the current date with the nextRefreshDate parameter as set in nCino Config in the Setup > nCino Setup folder. A check is made to ensure the refresh token is properly updated in nCino.

Test case structure:

{
  "test case name": {
      "Result": "string", // test status - defined below
      "Message": "string", // custom message
      "Process": "string" // process ID - only for error and failed statuses
  }
}

Test cases results statuses:

  • Failed: the entire test case has failed
  • Passed: the test case has passed
  • Error: test case not completed or missing information

Configuration

Note

Before running the health checks please make sure the following steps have been carried out:

  1. Configure products in both Mambu and nCino as described in Products configuration in MPO
  2. Install and configure the connector, completing all steps listed in Installation and configuration

Test case result examples

  1. All tests are successful

    {
    "mambuConnectivity": {
        "Result": "Passed",
        "Message": "Connectivity between MPO and Mambu is successful!"
    },
    "mambuProducts": {
        "Result": "Passed",
        "Message": "All Config Deposit Product keys exist in Mambu"
    },
    "nCinoConnectivity": {
        "Result": "Passed",
        "Message": "Connectivity between MPO and nCino is successful!"
    },
    "nCinoEndpoints": {
        "Result": "Passed",
        "Message": " nCino package in Salesforce is properly installed."
    },
    "nCinoProducts": {
        "Result": "Passed",
        "Message": "All Config Deposit Product keys exist in nCino"
    },
    "nCinoRefreshToken": {
        "Result": "Passed",
        "Message": "RefreshToken has been properly updated."
    }
    
  2. Test cases with error or failed results

    • In cases with error, the test case result will be Error and the message parameter will describe the issue:
    {
        "nCinoProducts": {
            "Result": "Error",
            "Message": "Something went wrong with nCino connectivity or config SD. Deposit product list from nCino could not be retrieved.",
            "Process": "64214"
        }
    }
    
    • In failed cases, the test case result will be Failed and the message parameter will describe the issue:
    {
        "mambuConnectivity": {
            "Result": "Failed",
            "Message": "Mambu connectivity failed: INVALID_TENANT_ID ",
            "Process": "64211"
        }
    }