Daily Maintenance Visibility

General

In order to keep loans up-to-date, automate communications, and apply rules, LoanPro runs a daily (or, more accurately, nightly) process to apply the next days interest, update the archive reports, run the calculator, etc. We refer to this process as Daily Maintenance. LoanPro offers some visibility into what happened during this process, so clients can know when the process has been completed, and generally what the process did.

Report

You can find the Daily Maintenance report by navigating to My Account > Billing & Statements > Daily Maintenance

This report shows

  • Day of the Month - The day for which data is shown
  • Queued Time - The time when Daily Maintenance was queued
  • In Progress Time - The time when Daily Maintenance started processing the tenant
  • Completed Time - The time when Daily Maintenance finished processing the tenant
  • Queued Loans - The total number of loans eligible to be processed by Daily Maintenance (non-archived loans in the tenant)
  • Loans Maintained - The total number of loans processed by Daily Maintenance

You can filter results by month and year using the filter drop-downs at the top left of the report.

Event-Based Notifications

There are three event-based notifications that can be used to notify you about Daily Maintenance. These include:

  • Daily Maintenance Queued - Your tenant has been added to the queue so that Daily Maintenance can run on your tenant and accounts.
  • Daily Maintenance In Progress - Daily Maintenance is running on your tenant and is updating your accounts.
  • Daily Maintenance Completed - Your tenant and all of your accounts have been updated by Daily Maintenance.

API

Information about Daily Maintenance can be pulled through the API. The API endpoint is:

https://loanpro.simnang.com/api/public/api/1/odata.svc/TenantDMStats

This endpoint will return Daily Maintenance information for all of the days that have been recorded for the tenant. The information for each day will look like this:

{ "__metadata": 
{ "uri": "http://loanpro.simnang.com/api/public/api/1/odata.svc/TenantDMStats(id='14',date=datetime'2021-03-19')", "type": "Entity.TenantDMStats"
},
"id": "14",
"date": "/Date(1616112000)/",
"queued": "/Date(1616133984)/",
"inProgress": "/Date(1616133988)/",
"completed": "/Date(1616139970)/",
"totalLoans": 447,
"maintainedLoans": 447
}

This information includes:

  • id - An ID for the record
  • date - The date and time for this record
  • queued - The date and time when Daily Maintenance was queued
  • inProgress - The date and time when Daily Maintenance started processing the tenant
  • completed - The date and time when Daily Maintenance finished processing the tenant
  • totalLoans - The total number of loans eligible to be processed by Daily Maintenance (non-archived loans in the tenant)
  • maintainedLoans - The total number of loans processed by Daily Maintenance

Note: All dates and times are in UTC and will be returned in epoch format.

If you would like to get this information for a specific date, an OData filter or other parameters can be added to the endpoint URL.

For example:

https://loanpro.simnang.com/api/public/api/1/odata.svc/TenantDMStats?$filter=date%20ge%20datetime%272021-03-17%27%20and%20date%20le%20datetime%272021-03-17%27&$orderby=date

Using the $filter token and the $orderby token will let you specify a date range for which information will be returned and the property that will be used to sort the data.


How did we do?


Powered by HelpDocs (opens in a new tab)