Data Mapper Transform for PDF and Docusign
How to build a Data Mapper Transform that reshapes JSON with output data types and fills a PDF or a Docusign template: Target PDF rules, the Omniscript PDF Action's properties, Docusign data labels and tabs:textTab paths, and hand-built input JSON.
Configure the Transform interface type to prepare data for downstream use (JSON, etc.) or document generation (PDF, Docusign).
~8 min read · 8 practice questions ·
What the exam expects
- Configure a Data Mapper Transform to reshape JSON for downstream use: map input paths to output paths, set Output Data Types and handle null values.
- Build a PDF Transform (Input Type JSON, Output Type PDF, Target PDF) and prepare a form that meets the PDF requirements.
- Configure the Omniscript PDF Action: Document, PreTransform Data Mapper, attachment properties, Read Only, date formats and
useAppearanceObject. - Prepare a Docusign template with data-labelled custom fields and map Omniscript data to
tabs:textTabpaths. - Build a Transform's input JSON by hand or from Preview so its paths match the Omniscript data structure.
Key terms: Transform (reshapes data in memory, never reading or writing Salesforce objects), Target PDF (the uploaded fillable form a PDF Transform fills), PDF Action (the Omniscript action that fills the PDF), PreTransform Data Mapper (the PDF Action picklist naming the Transform), data label (a Docusign custom field's name in the Transform), Output Data Type (the type a mapping casts its value to).
Key facts
- Detail
- No; it works in memory without SOQL
- Detail
- No node unless Include null values in the response is selected
- Detail
- Object deserializes a string; JSON serializes, omit it for JSON output
- Detail
- Only the first element is output
- Detail
- Fillable, Linearized 1.5 or above, no List Box fields, Latin-1 only
- Detail
- Date Format MM/DD/YYYY in moment.js notation
- Detail
"useAppearanceObject": truein the PDF Action JSON editor
- Detail
- Read access to the Data Mapper Bulk Data object
- Detail
- Over 250KB slow; over 1MB minutes, sometimes times out
- Detail
- Text, Radio Button, Checkbox custom fields with data labels; no standard or prefill fields
- Detail
tabs:textTab:<data label>
Sources for this section (6)
- Data Mappershelp.salesforce.com (opens in a new tab)
- Transform mappingshelp.salesforce.com (opens in a new tab)
- Output Data Typeshelp.salesforce.com (opens in a new tab)
- Fill a PDFhelp.salesforce.com (opens in a new tab)
- Prepare DocuSignhelp.salesforce.com (opens in a new tab)
- Docusign Transformhelp.salesforce.com (opens in a new tab)
- Why can't a Docusign standard field receive Omniscript data?
- When should a support admin check the Data Mapper Bulk Data object?
- Why would a Transform output have no node for a blank field?
- How do you build a Docusign Transform's input without running the Omniscript?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 46 lessons of the Omnistudio Developer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (8 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams