# About Relationships, Renditions & Lifecycles for Approved Email

The Approved Email feature includes special configurations for relationship types, rendition types, and lifecycles that apply only to Approved Email document types. These relationship and rendition types support specialized functionality to perform actions such as resolving a document link like {{PILink}} into a link to the target document of the _Related PI_ relationship for a specific email fragment.

<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>: Approved Email integrates with PromoMats and MedComms applications. Some configuration options must be enabled by Veeva Services. To import and activate all Approved Email components in Vault, contact Veeva Services.</p>
    </div>
  </div>
</div>



## Relationship Types for Email Templates & Email Fragments {#relationship-types}

These relationship types are available for the _Email Templates_, _Email Fragment_, and _Master Email Fragment_ document types:

  * _Related Pieces_ (PromoMats only) links a related promotional piece and only allows a single target document. When <a href="/en/gr/12080/#automatically-create-fragments">**Publish Approved Email Fragments for Veeva CRM**</a> is enabled, the relationship is version-specific. _Related Pieces_ are available to view in the external viewer.
  * _Related Medical Content_ (MedComms only) links related medical content and only allows a single target document. When <a href="/en/gr/12080/#automatically-create-fragments">**Publish Approved Email Fragments for Veeva CRM**</a> is enabled, the relationship is version-specific. _Related Medical Content_ are available to view in the external viewer.
  * _Based On_ links _Email Fragment_ documents to the _Master Email Fragments_ they were created from and only allows a single target document.
  * _Related PI_ links related prescribing information and only allows a single target document.
  * _Related ISI_ links related important safety information and only allows a single target document.
  * _Other_ links related documents with any document type and allows multiple target documents. 

<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>: You cannot add <em>Multichannel Presentation</em> or <em>Multichannel Slide</em> documents as related documents on <em>Email Templates</em>.</p>
    </div>
  </div>
</div>



## Relationship Types for Email Templates

In addition to the relationship types for linking content documents, the _Related Email Fragments_ relationship type exists for the _Email Templates_ document type. This relationship type allows you to link specific email fragments that Approved Email will allow users to select for a given email template. If you use this relationship, administrators in Veeva CRM can configure their settings to ensure CRM end users can only select the email fragments in this relationship.

The _Related Secure Message Notification_ document relationship type also exists for the _Email Templates_ document type. This relationship type allows you to link a single _Email Template_ with a _Secure Message Notification Template_, which then is transferred to Vault CRM to distribute a secure message via Approved Email.

## Rendition Types

All Approved Email-related document types have special rendition types:

  * **Assets**: The _Assets_ rendition is a ZIP file containing images used within the email template, email fragment, master email fragment, or template fragment. The ZIP file can contain a directory structure if needed. Uploading this ZIP file allows the document (email template, etc.) to reference images using relative URLs. These images are immediately published to a public web server. Although the URL to the images are obfuscated it is not recommended that any sensitive images are uploaded as email assets. Vault only processes images used in "img" tags, not those referenced in CSS/"style" tags.
  * **Veeva HTML**: The _Veeva HTML_ rendition is an HTML file that uses the special markup language and tokens available for linking Vault documents and pulling in other information (metadata, etc.) from the Vault.
  * **Veeva Preview**: The _Veeva Preview_ rendition is automatically generated by Vault. It is intended for use by the CRM application. The _Veeva Preview_ in-lines all the referenced assets into the HTML. Although this results in a much larger file size, it makes it easier for the CRM Client application to download the templates for offline use.
  * **Email Editor**: If your Vault uses the BEE email template editor, the _Email Editor_ rendition holds the formatting information needed to edit your template with BEE. An Admin must <a href="/en/gr/3037/#viewing">apply this rendition type</a> to the _Email Template_ document type.
  * **Preview Email**: If your Vault <a href="/en/gr/36971/">uses Litmus to preview emails</a>, the Preview Email rendition shows previews of your _Email Template_-type documents on a variety of devices and browsers.

## Approved Email Lifecycle

Veeva Approved Email provides a default lifecycle for _Email Template_, _Email Fragment_, _Master Email Fragment_, and _Template Fragment_ documents.

The _Approved Email_ lifecycle supports a staging and approval process. The templates start in _Draft_ state, and then move to _Staging_ for testing. After testing, users can move the templates into _Approved_ state and they become available for use in the Approved Email user interface. Users can then move templates into the _Deleted_ state, which marks them for deletion. Users can restore these templates if needed.

To preview your email templates on different devices, an Admin will need to <a href="/en/gr/36971/">configure a Preview Email user action</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>: Approved Email requires that you use the default lifecycle and states.</p>
    </div>
  </div>
</div>



## Document Link Expiration

Although the Approved Email viewer only presents the latest approved content to the email recipient, your organization may also need to ensure that the link sent in the email expires after a period of time. To support this need, Admins can choose an expiration period for the authentication tokens which are automatically embedded in each document link sent through Approved Email. Recipients who try to open a document via an expired link see a "document not found" message.

The expiration period is editable from **Admin** > **Settings** > **Application Settings**.

## Product Mapping

When using Approved Email, it's important that <a href="/en/gr/25318/">products are set up properly</a> in both Vault and CRM.