Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
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.

Code Block
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.

Code Block
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.

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

Reset Configurations UI Alignment

Validation | Track Everything

Code Block
"item_inspection_policy": "all"

will produce the same results as a

inspect_all

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

Validation tab in the UI when both of these options are checked

  • Inspect filtered items

  • Inspect shared items

makes the same call as

inspect_all

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

Validation tab in the UI when this item is checked

  • Inspect filtered items

makes the same call as

inspect_filtered

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

Validation tab in the UI when this item is checked

  • Inspect shared items

makes the same call as

inspect_shared

Code Block
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