/
Item Inspection Policy (REST API)

Item Inspection Policy (REST API)

On This Page

Overview

The Item Inspection Policy allows you to control the level of tracking and reporting for content that exists on both the source and destination platform, including content that has been configured to be excluded from transfer and content that existed on the destination prior to the initial transfer. This feature categorizes items for reports on the job Validation tab. The inspection policy can be set for a job through the REST API within the job transfer block with the "item_inspection_policy" parameter. Items that have been ignored/skipped by policy or not shown because they already existed on the destination can now be seen on reports with the defined categories. All job types and transfer directions support validation.

The available inspection policy options are:

  • none (default)

  • all

  • filtered

  • flagged

  • shared

If the connection does not have access to a given folder in a hierarchy, DryvIQ cannot track and report the items.

None (Default)

None is the default inspection policy configuration. This option does not need to be configured through the REST API; it is the system default. This inspection policy will not track all items but will offer additional tracking with performance in mind. It tracks all items on the source except filtered items (items ignored/skipped through the job filters). For the destination, all content in the root (files and folders) that existed prior to the initial transfer will be tracked as destinatio