...

The available inspection policy options are:

• flagged filtered (Default)

• all

• filteredflagged

• none

• shared

...

Filtered (Default)

Flagged Filtered is the default validation configuration. This option does not need to be configured in the application user interface or through the REST API; it is the system default. This The validation option to inspect filtered content will track items that have been flagged during transfer. It will track only flagged content that is not in a retry status. ignored/skipped based on the job filters. This option has the following features:

• This option can be configured via the REST API or in the application user interface through the Advanced Scripting option when creating a job.

• Source: Flagged content Filtered content configured to be skipped/ignored through job policies will be tracked.

• Destination: Content on the destination is not tracked for jobs that migrate in one direction from source to destination.

• Job type Sync: The destination will behave like the source.

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

"transfer": {
"item_inspection_policy": "

filtered",
"item_inspection_policy_next": "

filtered"
 }

All

The validation option to inspect all will track all content at all levels in the hierarchy on both the source and destination; including items configured to be ignored/skipped through job policies and items that existed on the destination prior to the initial transfer.

...

"transfer": {
"item_inspection_policy": "all",
"item_inspection_policy_next": "all"
 }

...

Flagged

The This validation option to inspect filtered content will track items that have been ignored/skipped based on the job filtersflagged during transfer. It will track only flagged content that is not in a retry status. This option has the following features:

• This option can be configured via the REST API or in the application user interface through the Advanced Scripting option when creating a job.

• Source: Filtered content configured to be skipped/ignored through job policies Flagged content will be tracked.

• Destination: Content on the destination is not tracked for jobs that migrate in one direction from source to destination.

• Job type Sync: The destination will behave like the source.

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

"transfer": {
"item_inspection_policy": "

flagged",
"item_inspection_policy_next": "

flagged"
 }

None

The “none” validation option will not track all items but will offer additional tracking with performance in mind. It will track all items on the source at all levels of the hierarchy but not including those configured to be ignored / skipped through policy. For the destination, all content in the root (files and folders) that existed prior to the initial transfer will be tracked as destination only items and reported as ignored/skipped.

...