# Merge to In-Flight Case

In Vault, an in-flight _Case_ is any open _Case_ that is still being processed. Generally, this includes _Cases_ in any state before _Approved_, _Closed_, or _Superseded_. As a Case Processor, you can merge new information from an _Inbox Item_ to an in-flight _Case_. Vault creates an <a href="/en/gr/907890/">_Inbound Transmission_</a> with links to the _Case_ and _Inbox Item_. Upon merge, Vault updates the latest _Case_ version to add a minor (+0.1) version number. For example, a _Case_ with version (v1.0) becomes (v1.1).

If multiple _Inbox Items_ link to the same _Case_, Vault updates them so that they all link to the new _Case_ version upon promoting an _Inbox Item_ to follow-up. This ensures that related _Inbox Item_ information is not lost on subsequent versions.

If your Admin has configured your Vault to isolate blinded product information on Clinical Trial _Study Cases_, see <a href="/en/gr/691317/#creating-follow-up-or-merging-to-current-study-cases">Creating Follow-Up or Merging to Current Study Cases</a> for additional considerations when completing these actions. For information on how Vault maps Japan-specific objects and fields when merging an imported file to an in-flight _Case_, see <a href="/en/gr/735519/#merge-to-in-flight-and-promote-to-follow-up-cases">PMDA E2B(R3) Case Import</a>.

## Prerequisites

To use the Merge to In-Flight feature, your Admin must:

* Enable the <a href="/en/gr/740208/#merge">_Merge to Active Case Version_ setting</a>.
* Perform the merge to in-flight _Case_ configurations in the <a href="/en/gr/01339/">enablement instructions</a>.

## Merge an Inbox Item to an In-Flight Case

When merging an _Inbox Item_ that has a link to an in-flight _Case_ and is in the _Marked for Follow-Up_ state, Vault skips duplicate detection and directs you to the _Inbox Item to Case Compare_ page. When merging an _Inbox Item_ that is not linked to a _Case_, Vault directs you to duplicate detection. From this page, you can select **Compare Details** to get to the _Inbox Item to Case Compare_ page.

<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 prevents you from merging an <em>Inbox Item</em> to an in-flight <em>Case</em> that is locked to another user. However, you can still create a Follow-up version from the <em>Inbox Item to Case Compare</em> page.</p>
    </div>
  </div>
</div>



To merge data on an _Inbox Item_ into an in-flight _Case_:

1. Navigate to the _Inbox Item_ <a href="/en/gr/01136/#mark-followup">marked for follow-up</a>.
2. From the **All Actions** menu, select **Promote to Follow-up**.
3. On the <a href="/en/gr/826980/">_Inbox Item to Case Compare_</a> page, select the information from the _Inbox Item_ you want to merge into the _Case_.
4. To complete the merge, select the **Merge to Current** icon.

<a href="https://platform.veevavault.help/assets/images/saf-merge-to-current.png" data-lightbox="saf-merge-to-current.png" data-title="Case Compare Merge to Current" data-alt="Case Compare Merge to Current">
  <img class="docimage" src="https://platform.veevavault.help/assets/images/saf-merge-to-current.png" alt="Case Compare Merge to Current" style=""  />
</a>

<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>: If you do not see the <em>Merge to Current</em> icon, this may be because of one (1) of the following reasons</p>

<ul>
  <li>The <em>Case</em> you want to merge into is in a prohibited state.</li>
  <li>You do not have edit access to the in-flight <em>Case</em> in its current state. Contact your Admin to grant you edit access.</li>
  <li>The <em>Localization</em> values on the <em>Inbox Item</em> and <em>Case</em> prevent them from being merged. Vault does not allow merging Global <em>Inbox Items</em> into <em>Domestic Cases</em>.</li>
</ul>
    </div>
  </div>
</div>



**Result**

Vault adds your selected changes on the _Inbox Item to Case Compare_ page to the latest _Case_ version. If the merge changes the primary designation for _Case Product_, _Adverse Event_, or _Case Contact_, those are applied to the latest _Case_ version. If the primary _Case Product_ or _Adverse Event_ changes, Vault reevaluates _Case Assessments_, _Expectedness_, and _Assessment Results_. The _Inbox Item_ state goes from _Marked as Follow-Up_ to _Promoted_ and a new section, _Inbox Item has been promoted_, appears with a link to the new _Case_ version. 

Depending on your <a href="/en/gr/1007670/">Admin's configuration</a>, if your changes create any _External Products_ on the _Case_, Vault may attempt to <a href="/en/gr/01165/#auto-code">auto-code the products using the WHODrug dictionary</a>.

<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>: When merging to an in-flight <em>Case</em>, the <em>New Info Date</em> is never updated after the merge. This supports retaining compliant <em>Transmission Due Dates</em>.</p>
    </div>
  </div>
</div>



For information on how Vault merges _Case_ narratives, see <a href="/en/gr/01167/">Generate a Case Narrative</a>.