On This Page
Overview
The job resets related to validation inspect options allow a job execution to traverse all folders, including those that are ignored/skipped due to policy, to record information about that folder for tracking and reporting for both the source and the destination.
This feature operates the Job Validation Report | item_inspection_policy.
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
Validation | Track Everything "item_inspection_policy": "all" | will produce the same results as a | inspect_all PATCH {{url}}v1/jobs/{{job}}?reset=inspect_all
|
Validation tab in the UI when both of these options are checked
| makes the same call as | inspect_all PATCH {{url}}v1/jobs/{{job}}?reset=inspect_all
|
Validation tab in the UI when this item is checked
| makes the same call as | inspect_filtered PATCH {{url}}v1/jobs/{{job}}?reset=inspect_filtered
|
Validation tab in the UI when this item is checked
| makes the same call as | inspect_shared 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 itemdestination_exists = false
This means DryvIQ has identified but did not transfer the item