---
category: [Administration & Integrations, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions, Platform and Product Extensions/Integration]
keyword: [Extend, Orchestration Builder, Orchestrate, Orchestration]
nav: wcp_docs
parent_url: /wcp_docs/
title: >- 
  Reference: Store Document
layout: subsection
---

## Purpose

Use this component to create a persistent copy of a document that:

-   Is available to other users.
-   Can optionally be attachment to an integration event in the tenant.


## <a id="section_2"></a>Availability

This component is available in these orchestration templates:

-   Business Process
-   Integration System
-   Suborchestration


It's also available in suborchestrations.

## Properties

Provide a meaningful <b>Reference Name</b> for the step as it will appear in your orchestration.

<b>General Tab</b>

In the <b>Document to Store</b> field, use <b>Expression Builder</b> to specify the document that you want to store.

Provide the <b>Document Title</b> that the document will be stored under and, optionally, a <b>Description</b>.

You can use the <b>Collection to Store Document In</b> field to specify a particular collection where the document is stored. If you don't specify a collection, Workday uses:

-   The integration event WID, in Integration System orchestrations.
-   The orchestration instance ID, for other templates.


You can provide an optional <b>Reference ID</b> to group related documents by giving them the same reference ID value. The Find Documents step retrieves documents by matching this value. If you don't specify one, Workday uses the orchestration instance ID.

Use the <b>Storage Expires In</b> expression field to specify how long Workday should persist the document. String expression must evaluate to ISO 8601 Duration. Examples: P7D for 7 days, P1M for 1 month.

<b>Integration Event Tab</b>

Use the <b>Integration Event Source</b> prompt to select which integration event you want to associate the stored document with:

<table><thead><tr><th>Option</th><th>Availability</th><th>Description</th></tr></thead><tbody><tr><td><b>Use Launch Event</b></td><td>Workday Integration System template and suborchestrations opened by an Integration System.</td><td>Associates the document with the integration event that launched the orchestration. <p>Default for the Workday Integration System template.</p></td></tr><tr><td><b>Custom Integration Event</b></td><td>All templates.</td><td>Reveals an <b>Integration Event</b> field where you provide an expression that resolves to an integration event reference.</td></tr><tr><td><b>None</b></td><td>All templates other than Workday Integration System and suborchestrations opened by an Integration System.</td><td>The document is stored with no integration event association. <p>Default for all templates other than Workday Integration System.</p></td></tr></tbody></table><br/>

By default in Integration System orchestrations, the stored document isn't attached to the integration event. To override this, change the boolean value in the <b>Attach document to integration event</b> field to <i>true</i>.

When the document is associated with an integration event, you can select <b>Deliver from associated delivery services</b> to use any delivery services configured to route documents to a target endpoint.

When the document is associated with an integration event, you can also set these optional metadata fields on the event document:

<table><thead><tr><th>Field</th><th>Description</th></tr></thead><tbody><tr><td><b>Owner</b></td><td>An instance reference to the account that owns the document.</td></tr><tr><td><b>Content Type Reference</b></td><td>An instance reference to the content (MIME) type of the document, such as <code>application/pdf</code>.</td></tr><tr><td><b>Document Type Reference</b></td><td>An instance reference to the Workday document type.</td></tr><tr><td><b>Severity</b></td><td>The severity recorded on the integration message: DEBUG, INFO, WARNING, ERROR, or CRITICAL.</td></tr><tr><td><b>Secured Instances</b></td><td>A list of instance references, such as pay groups or cost centers, that access to the document is evaluated against at retrieval time. Applies only to documents attached to Cloud Connect for Third-Party Payroll or Payroll Effective Change Interface connector integration events. <p>Example: Use this field so that information for a pay group is only accessible by a payroll partner with role-based access to that pay group. This allows a single integration event to contain attachments for multiple pay groups while ensuring that individual attachments are only accessible to users with the required security.</p></td></tr></tbody></table><br/>

You can add optional <b>Tags</b> to label your stored documents. Tags are only valid if they've already been created in the tenant.

<b>Settings Tab</b>

Configure these request and response details:

-   <b>Overall Timeout</b>: The total time allowed for the operation. The default value is 300 seconds.
-   <b>Connect Timeout</b>: The time allowed for a client-server connection to establish. The default value is 10 seconds.
-   <b>Response Timeout</b>: The total time allowed for receiving a response. The default value is 20 seconds.
-   <b>Retry Settings</b>: Select a predefined retry policy.


## Output

If the step is successful, the component outputs the `entryId` of the stored document and the `refId` it was stored with, for use in later steps such as Retrieve Document.

### Related Information

[Reference: Find Documents](/wcp_docs/GUID-dd631824-a040-4169-ad7d-fea99fb363fb-enHYPHENus.html)

[Reference: Retrieve Document](/wcp_docs/GUID-5d3f983b-85f8-4c68-9b50-6993adbde13d-enHYPHENus.html)