This post explains what a footprint is and demonstrates how to create and troubleshoot a footprint for a particular inspection, and integrate that footprint into your report writing software.

What is a Footprint?

A 'footprint' in ISN is essentially a collection of all the basic information for an order, from the client information, to the inspection type, to the property's square footage, and any other data housed for that order in your ISN. A footprint acts as a flag to any third party software (typically report writers) to indicate "Hey! Here's some information about an inspection that you might need!" and allows them to pre-load the app with information directly from your ISN site!

Creating a Footprint 

Log in to your ISN, navigate to Inspections -- View Inspections to view the inspection grid.

Click the blue icon with the i for the inspection you need to create a footprint for.
Navigate to the Actions drop down button and then click Create Footprint

Alternatively you can go to Inspections -- My Footprints  and click the green + symbol to create a new footprint. 

Troubleshooting Footprints

 Footprints are automatically created for every order; however,  If an order is scheduled to a date and time in the past, then the footprint will not generate. Furthermore, a footprint will also get used up if and when it has been pulled into a report writer app.

If you ever come to experience particular issues of orders not properly populating in a report writer app, you'll want to check the order history of the order(s) to pinpoint the initial scheduled date and time. If the Order History log appears as the example shown below, then the order is considered to having been scheduled in the past.

You will also want to check whether the order(s) has or have already been pulled into a report writer app. Once you discover the cause of your issue, then you'll simply follow the aforementioned instructions for creating a footprint on said order(s).
Lastly, you'll navigate back to your report writer and repeat the steps to import that information over, and you'll be all set!

Did this answer your question?