# Working with Extensible Controlled Copies (QualityDocs)

QualityDocs users often require a way to track specific content copies outside of Vault, or prepare copies with specific overlays for specialized use. QualityDocs Vaults provide special user actions to assist with these use cases, supporting download, distribution, and reconciliation of controlled copies.

When downloaded, Vault assigns each controlled copy a unique identification number and creates a _Controlled Copy Trace_ object record, allowing you to track the status of those copies outside of the Vault. With a dedicated lifecycle for these object records, you can manage both the distribution and the reconciliation of these copies according to your organization's needs. Your Vault may also apply specialized overlays or attach signature pages on the content when you download controlled copies. Depending on the document lifecycle state and any additional configured conditions, there may be zero, one, or many controlled copy actions, for example, _Request Laboratory Reference Copy_ and _Request Facility Posting Copy_.


<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: The functionality in this article refers to object-based Extensible Controlled Copy, which must be <a href="/en/lr/50292/">configured</a> by a Vault Admin. See <a href="/en/lr/12369/">Distributing Controlled Copies</a> for information on working with legacy document-based controlled copies.</p>
    </div>
  </div>
</div>



## How Vault Manages Extensible Controlled Copies

With object-based Extensible Controlled Copies, Vault collects controlled copy information via configurable object records instead of through a static form. Capturing controlled copy information in object records allows for much more robust data collection, security, processes, and reporting options.

When you download a controlled copy, Vault opens the form to create a new _Controlled Copy User Input_ record within the dialog. In this dialog, you can enter data about the controlled copy request in the fields configured by your Admin. When you submit the controlled copy request, Vault generates a ZIP file containing your requested controlled copy and an associated manifest file. 

For each controlled copy, Vault also creates an associated _Controlled Copy Trace_ record and copies field data on the _Controlled Copy User Input_ record to each _Controlled Copy Trace_ record. You'll see a banner alerting you that the job is in progress, and you'll receive a Vault notification when the ZIP file is ready to download.

See details below about [potential errors][1] you may encounter while downloading a controlled copy.



<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Vault allows documents to be deleted from your Vault’s Library, as long as the related <em>Controlled Copy Trace</em> records are inactive, according to their <em>Status</em>. When <a href="/en/lr/50292/#enablement-setting">enabled</a>,  Vault also deletes these qualifying <em>Controlled Copy Trace</em> records.</p>
    </div>
  </div>
</div>



### About Controlled Copy Recall & Reconciliation

The *Controlled Copy Trace* object lifecycle is highly configurable to meet your organization's controlled copy process requirements. Veeva-recommended [configurations](/en/lr/50292/) for managing the recall or reconciliation process include:

* [Automatic][3] controlled copy recall when a document reaches a certain state, such as *Superseded* or *Obsolete*. This configuration additionally supports manual recall.
* [Manual][2] reconciliation of up to 100 records at a time via the **Controlled Copies for Reconciliation** page. This process can be further expedited with the page's scanning mode, which allows you to scan a document's QR or barcode and quickly locate its related *Controlled Copy Trace* record.

These options can be configured separately or together.

## Downloading Controlled Copies

To download a controlled copy:

  1. From the document's **All Actions** menu, select a controlled copy action. These actions vary based on your organization's configuration and may not contain "controlled copy" in the name.
  2. Vault opens the _Controlled Copy User Input_ dialog. The dialog title and fields that appear here will vary depending on your Admin's configuration.
  3. Fill in fields as needed.
  4. Click **Continue**. Vault asynchronously generates a ZIP file containing your requested copies. The ZIP file also includes a manifest PDF file listing the copy type, document name, and the requestor's name, followed by all user-entered fields in alphabetical order. You can download the file from your _Notifications_ page.

### Downloading Controlled Copies in Bulk

To request controlled copies from multiple documents via a bulk action, see [Using Bulk Document Actions](/en/lr/18822/#generate_controlled_copy).

## Reconciling Controlled Copies in Bulk {#reconciling-in-bulk}

You can manually recall up to 100 controlled copies at a time via the **Controlled Copies for Reconciliation** tab. When a document includes a QR code or barcode, this specialized page's scanning mode allows you to quickly locate its related *Controlled Copy Trace* record.

1. Navigate to the **Controlled Copies for Reconciliation** tab. This tab may appear with a different label depending on your Vault's configuration.
2. Vault displays all active *Controlled Copy Trace* records. 
    * Use the page's search bar or apply filters to locate the record(s) you'd like to recall, then click the left-hand checkbox next to each record.
    * When a document includes a QR code or barcode, click <i class="far fa-barcode-read"></i> **Select via scan** to enter scanning mode. Once you scan the code, Vault populates and selects the *Controlled Copy Trace* record, along with any records you manually selected.
1. Click **Continue**.
2. In the **Start Workflow** dialog, select the applicable multi-record object workflow (for example, "Controlled Copy: Recall"), then click **Continue**.
3. If required, populate any required fields (for example, **Reconciliation Notes**), then click **Start**.

Vault returns to the default **Controlled Copies for Reconciliation** page and displays the **Workflow** you initiated for each *Controlled Copy Trace* record. Once the workflow is complete and the record enters a state in which it becomes inactive (for example, "Recall Confirmed"), it is no longer available for selection on the page.

## About Automatic Controlled Copy Recall {#controlled-copy-recall}

The *Controlled Copy Trace* object lifecycle is highly configurable to meet your organization's controlled copy process requirements. The Veeva-recommended [configuration](/en/lr/50292/#configuring-automatic-controlled-copy-recall) allows for both automatic and manual recall such that:

* When a controlled copy is *Superseded* or made *Obsolete*, Vault automatically moves *Controlled Copy Trace* records to the *In Recall* state and initiates a workflow for the requesting user to reconcile the document which is no longer in use. 
    * Once complete, Vault moves the record to the *Recall Confirmed* state, where it becomes inactive.
    * As with many automated workflow configurations, Vault issues a single workflow per *Controlled Copy Trace* record during these operations, meaning a single document version with, for example, five related *Controlled Copy Trace* records results in five workflows for the requesting user(s) to reconcile. The [**Controlled Copies for Reconciliation**][2] tab and its [related configuration](/en/lr/50292/#controlled-copy-reconciliation) can expedite this process by allowing a single workflow to process multiple *Controlled Copy Trace* records.
* While a *Controlled Copy Trace* record is in its *In Recall* state, users can execute the **Confirm Reconciliation** action to manually recall that record. This state also includes an action to **Revert to Active**, where Vault moves the record back to the *Active in Use* state.

## Reporting

[Legacy controlled copy](/en/lr/12369/) _Distribution with Document_-type reports are not applicable for Extensible Controlled Copies. To report on Extensible Controlled Copy data, configure a report referencing _Controlled Copy Trace_ object records.

## Errors & Limitations {#errors}

In some cases, Vault may not be able to download controlled copies:

  * If there is a configuration error between the _Controlled Copy User Input_ and the _Controlled Copy Trace_ object types or records, Vault cannot successfully download controlled copies.
  * In most cases, Vault creates the _Controlled Copy Trace_ record even if there is an error downloading a copy or preparing the manifest file. In this case, Vault does not set the checkbox in the _Released from Vault_ field on the _Controlled Copy Trace_ record.
  * Vault reports any errors encountered when downloading a controlled copy in the delivered manifest file.
  * During the controlled copy bulk action, if Vault cannot create the _Controlled Copy User Input_ record, Vault will inform you on the _Confirmation_ page of the bulk action wizard.
  * Vault cannot download Extensible Controlled Copies for documents with password-protected source files.

## Related Permissions {#permissions}

See [Extensible Controlled Copy Configuration](/en/lr/50292/) for the permissions required to use this feature.

 [1]: #errors
 [2]: #reconciling-in-bulk
 [3]: #controlled-copy-recall