---
schema_version: "1"
id: 585ea5ed8b32ec6410891d3e17907685a4dac0b5671f9cd1435b9e34734618af
title: Add a PDF Action to an Omniscript (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_add_a_pdf_action_to_an_omniscript.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_add_a_pdf_action_to_an_omniscript.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3016ee9d56381682fbe06f155a0dfc2b4929344383abadd5e9cbf0b4c9cad059
description: For the managed package runtime, populate a PDF with Omniscript data using the PDF Action.
products:
  - Omnistudio
release: "264"
---
# Add a PDF Action to an Omniscript (Managed Package)

For the managed package runtime, populate a PDF with Omniscript data using the PDF Action.

![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png)

Note

The PDF Action is not supported in IE 11 browsers. Edit block doesn't support this action.

Beginning Spring ’22, enable older PDF viewers to display text fields in a PDF element using the appearance object property. By default, the `useAppearanceObject` is undefined. To enable, add "useAppearanceObject": true in the JSON editor of the PDF Action Properties pane.

PDFs larger than 250KB generate slowly. PDFs larger than 1MB can take several minutes to generate and sometimes time out.

Before You Begin

1. From the Omniscript Designer, drag the **PDF Action** to the Omniscript.
2. From the Properties pane, in **Document**, select your PDF document.
3. (Optional) Attach the PDF to a parent record by taking these steps:
    1. For **Attachment Name**, name the attachment.
    2. For **Attachment Parent Id**, provide the id of the attachment's parent record id.
4. In the Send Transformations section, from the **PreTransform Data Mapper Interface** picklist, select the Omnistudio Data Mapper that you created in [Create a Data Mapper Interface to Map an Omniscript to a PDF](https://help.salesforce.com/s/articleView?id=xcloud.os_create_a_dataraptor_interface_to_map_omniscript_data_to_a_pdf.htm&release=264.0.0&type=5 "For the managed package runtime, after you create the Omniscript and upload your PDF, you must create a Data Mapper to map the information from the Omniscript to the PDF.").
5. Select **Read Only** to make the filled PDFs read-only.
6. If necessary, change the default date and time formats.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png)
    
    Note
    
    Use [moment.js](http://www.momentjs.com) formatting. If left blank, the defaults are Time Format: h:mm a, Date Format: MM/DD/YYYY, Date Time Format: MM/DD/YYYY h:mm a.
7. Exclusive to the Classic Designer, if you bypass the redirect page, the filled PDF file will be open in a separate tab. Specify a display height and width for the dimensions of the tab. If you do not see the fields being filled until you click into them, you may need to disable the "Highlight Existing Fields" option in the Adobe Acrobat preferences.
8. Launch the form in Preview mode, and fill out each field that should map to the PDF.
9. Check the PDF to confirm the mappings are correct.