...

On This Page

Overview

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 or within the job transfer block with "item_inspection_policy." 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.

...

Default Configuration: "item_inspection_policy": "none"

The default validation option is inspect none. 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 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.

...

• This option does not need to be configured 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 policy will not be tracked. If the connection does not have access to a given folder in the hierarchy, we cannot track and report these items.

• 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.

• Destination: All content (files & folders) in lower depths of the directory (sub-folders) that existed prior to the initial transfer will not be tracked.

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

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

• Job Reports - Validation tab: At any time, you may run a validation run which will trigger a full inspection of all content relating to the option you select for the next run only.

...

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

Track Everything | "item_inspection_policy": "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 policy 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 JSON block.

• Source: All content in the root, folder, and subfolder directories including those configured to be skipped/ignored through policy 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 policy 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 cannot track and report these items.

...

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

Content Reconciliation

The content reconciliation provides a comparison of the reconciled items between the source and destination. It can help track the success of the migration. By default, it shows the counts for files and folders, but you can choose to view just folders, just folders, or data. It reports on the following information:

• Identified: This is the totals count of items or data identified on the source and destination (including flagged/retried items).

• Ignored destination only items: This is the count of the items ignored on the destination and the percentage of the overall content theses items make up.

• Ignored [Filter]: If filters were added to the job to exclude content, any entry for each filter is included in this section. It will identify the count of the filtered items and the percentage of the overall content theses items make up.

• Successfully matched or transferred (Including flagged and revised): This is the count of items or data that have been successfully matched or transferred between the course and destination.

...

Transfer Stats, By Inspection

GET {{url}}v1/transfers/{{job_id}}/stats/by_inspection

...

Validation Reset Options Through the REST API

inspect_filtered

This job reset will reevaluate all filtered content on both the source and destination in the next job run after the reset is executed, including content ignored due to policy configured for job filters, hidden, and content shared to the transfer owner.

PATCH {{url}}v1/jobs/{{job}}?reset=inspect_filtered

inspect_shared

This job reset will reevaluate all shared content on both the source and destination in the next job run after the reset is executed, including content ignored due to policy configured to excluded data not owned by the transfer author/owner.

PATCH {{url}}v1/jobs/{{job}}?reset=inspect_shared

inspect_all

This job reset will reevaluate all content on the source and destination in the next job run after the reset is executed, including content ignored due to policy configured for filters and shared.

PATCH {{url}}v1/jobs/{{job}}?reset=inspect_all

Reset Configurations UI Alignment

"item_inspection_policy": "all"

PATCH {{url}}v1/jobs/{{job}}?reset=inspect_all

PATCH {{url}}v1/jobs/{{job}}?reset=inspect_all

PATCH {{url}}v1/jobs/{{job}}?reset=inspect_filtered

PATCH {{url}}v1/jobs/{{job}}?reset=inspect_shared

Export Items Report in the User Interface

In the DryvIQ Platform, the exported items report will have a status column where skipped content will be recorded. For each skipped entry, observe the value for the source_exists and destination_exists columns.

• source_exists = true
  This means DryvIQ has identified the skipped item

• destination_exists = false
  This means DryvIQ has identified but did not transfer the item