# Downloading Extensible Controlled Copies (Document Control)

<!--- Comment:  If anyone updates this article for a feature, ping the corresponding Quality writer because the code is still (mostly) shared. --->

QualityOne users often require a way to track specific content copies outside of Vault, or prepare copies with specific overlays for specialized use. <a href="/en/gr/78612/">QualityOne Vaults</a> provide special user actions to assist with these use cases, supporting the download and distribution 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, there may be zero (0), one (1), or many controlled copy actions, for example, _Request Laboratory Reference Copy_ and _Request Facility Posting Copy_.

Depending on your <a href="/en/gr/61202/">Admin's configuration</a>, object, field, and section labels may appear differently than the labels mentioned in this article.


<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. See <a href="/en/gr/78806/">Distributing Legacy Controlled Copies</a> for details on working with legacy document-based controlled copies.</p>
    </div>
  </div>
</div>



## How Vault Downloads Extensible Controlled Copies {#vault-download}

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. Vault also creates an associated _Controlled Copy Trace_ record for each controlled copy you requested, and copies data from the fields 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 about [potential limitations][1] you may encounter while downloading a controlled copy.

## How to Download Controlled Copies {#download}

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. Fill in fields as needed in the _Controlled Copy User Input_ dialog.
3. 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.

## Download Controlled Copies Bulk Action {#download-bulk-action}

To request controlled copies from multiple documents via a bulk action, see <a href="/en/gr/18822/#generate_controlled_copy">Using Bulk Document Actions</a> for more details.

## Obsolete and Superseded Controlled Copies {#obsolete-superseded}

If configured by your Admin, when a document with controlled copies in circulation enters an _Obsolete_ or _Superseded_ state, Vault puts all its controlled copies into an _In Recall_ state and auto-starts a recall workflow that issues a task to the person responsible for reconciling each issued copy. 

## Reporting {#reporting}

Legacy controlled copy _Distribution with Document_ type reports are not applicable for Extensible Controlled Copies. To report on Extensible Controlled Copy data, <a href="/en/gr/3606/">create a report</a> referencing _Controlled Copy Trace_ object records.

## Limitations {#errors}

The following limitations apply to Extensible 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 will create 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.
* When running the [controlled copy bulk action][2], if Vault cannot create the _Controlled Copy User Input_ record, Vault will inform you on the _Confirmation_ page when running the bulk action.
* Vault cannot download Extensible Controlled Copies for documents with password-protected source files.

[1]: #errors
[2]: #download-bulk-action