...

The available inspection policy options are:

• none flagged (Default)

• all

• filtered

• flaggednone

• shared

None

...

Flagged (Default)

Flagged 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 configuration validation option will not track all items but will offer additional tracking with performance in mind. Inspect none 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 & folders) that existed prior to the initial transfer will be tracked as destination only items and reported as ignored/skipped.items that have been flagged during transfer. It will track only flagged content that is not in a retry status. This option has the following features:

• This option does not need to can be configured via the REST API or in the application user interface or through the REST API; it is the system default. Jobs created in previous releases will now assume this settings after upgrade. A soft reset will be required to align the validation chart calculations using the inspect none configuration.

• Source: All content (files & folders) at all levels in the hierarchy will be tracked; items configured to be ignored/skipped through job policies will not be tracked. If the connection does not have access to a given folder in the hierarchy, DryvIQ cannot track and report these items.

• 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. All content (files and folders) in lower depths of the directory (subfolders) that existed prior to the initial transfer will not be trackedAdvanced Scripting option when creating a job.

• Source: 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"
 }

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.

...

• 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: All content in the root, folder, and subfolder directories including those configured to be skipped/ignored through job policies and items that existed on the destination prior to the initial transfer will be tracked.

• Destination: All content in the root, folder, and subfolder directories including those configured to be skipped/ignored through job policies and items that existed on the destination prior to the initial transfer will be tracked.

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

...

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

...

None

The validation option to inspect flagged content will track items that have been flagged during transfer. “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.

This option has the following features:

• This option can does not need to be configured via the REST API or in the application user interface through the Advanced Scripting option when creating a jobor through the REST API; it is the system default. Jobs created in previous releases will now assume this settings after upgrade. A soft reset will be required to align the validation chart calculations using the inspect none configuration.

• Source: Flagged content will be tracked.Destination: Content on the destination is not tracked for jobs that migrate in one direction from source to destinationAll content (files and folders) at all levels in the hierarchy will be tracked; items configured to be ignored/skipped through job policies will not be tracked. If the connection does not have access to a given folder in the hierarchy, DryvIQ cannot track and report these items.

• 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. All content (files and folders) in lower depths of the directory (subfolders) that existed prior to the initial transfer will not be tracked.

• 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": "

none",
"item_inspection_policy_next": "

none"
 }

Shared

The validation option to inspect shared content will track items that have are shared. This option has the following features:

...