---
schema_version: "1"
id: 48bcb11b94b0ae3408ace9db4e8eccbee363641ee7132350a5de857b43ce35fe
title: Step Properties for the fndmultiDocxLwc Omniscript
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/doc_gen_fndmultidocxlwc_omniscript_structure_394764.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.doc_gen_fndmultidocxlwc_omniscript_structure_394764.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f8ee8ddad7f6a2e5ad94bf9aff56a75990f0fdfc4a0cdc1152ea0e8db2b54eed
description: The fndmultiDocxLwc Omniscript contains of steps, which run sequentially when you invoke the Omniscript. Each step has properties that determine the action that the step performs. If you want to change the steps, Salesforce recommends that you either create a version or clone and rename a copy of the fndMultiDocxLwc Omniscript.
products:
  - Omnistudio Document Generation
release: "264"
---
# Step Properties for the fndmultiDocxLwc Omniscript

The fndmultiDocxLwc Omniscript contains of steps, which run sequentially when you invoke the Omniscript. Each step has properties that determine the action that the step performs. If you want to change the steps, Salesforce recommends that you either create a version or clone and rename a copy of the fndMultiDocxLwc Omniscript.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col>
        <col>
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d9167e26">
            <p style="margin-bottom:0;">Omniscript Step</p>
          </th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d9167e31">
            <p style="margin-bottom:0;">Properties</p>
          </th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="Omniscript Step" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e26 ">
            <p style="margin-bottom:0;">Script Configuration</p>
          </td>
          <td data-label="Properties" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e31 ">
            <p>Fields are preset.</p>
            <ul>
              <li>
                <strong class="uicontrol">Type</strong> docGenerationSample
              </li>
              <li>
                <strong class="uicontrol">SubType</strong> fndMultiDocxLwc
              </li>
            </ul>
          </td>
        </tr>
        <tr class="">
          <td data-label="Omniscript Step" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e26 ">
            <p style="margin-bottom:0;">Enter Object</p>
          </td>
          <td data-label="Properties" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e31 ">
            <ul>
              <li>
                <strong class="uicontrol">objectId</strong> Salesforce Object ID of the object on
                which the document is generated. The ObjectID is used in
                the&nbsp;SetValues&nbsp;step to set the contextID.
              </li>
              <li>
                <strong class="uicontrol">templateType</strong>&nbsp;Use either a Microsoft Word
                (.docx) document template or Microsoft PowerPoint (.pptx) document
                template.
              </li>
            </ul>
          </td>
        </tr>
        <tr class="">
          <td data-label="Omniscript Step" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e26 ">
            <p style="margin-bottom:0;">Get Document Templates</p>
          </td>
          <td data-label="Properties" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e31 ">Retrieves all active .docx or .pptx document templates (JSON Based) by using
            the&nbsp;DocGenSample-ExtractDocumentTemplatesLWC&nbsp;Omnistudio Data Mapper
            Interface.</td>
        </tr>
        <tr class="">
          <td data-label="Omniscript Step" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e26 ">
            <p style="margin-bottom:0;">Pick Template</p>
          </td>
          <td data-label="Properties" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e31 ">Captures multiple IDs of the templates in the DocumentTemplate selectable list by using the
            clmSelectableItems LWC component.</td>
        </tr>
        <tr class="">
          <td data-label="Omniscript Step" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e26 ">
            <p style="margin-bottom:0;">Set Values</p>
          </td>
          <td data-label="Properties" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e31 ">
            <p>Sets the required variables for document generation.</p>
            <ul>
              <li>
                <strong class="uicontrol">selectedTemplate</strong>:&nbsp;ID of the document template
                that's used for document generation.
              </li>

              <li>
                <strong class="uicontrol">templateType</strong>:&nbsp;Microsoft Word (.docx) or
                Microsoft PowerPoint (.pptx) document template.
              </li>

            </ul>
          </td>
        </tr>
        <tr class="">
          <td data-label="Omniscript Step" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e26 ">
            <p style="margin-bottom:0;">Arrange Selected Template</p>
          </td>
          <td data-label="Properties" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e31 ">Reorders the document templates that you select in the PickTemplate(s) step. It uses the
            <strong class="uicontrol">clmOsArrangeSelectedTemplateList</strong> LWC component, which
            uses Javascript to invoke Apex classes. When generating the document, you can
            select the templates that use their own DR Extract.
          </td>
        </tr>
        <tr class="">
          <td data-label="Omniscript Step" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e26 ">
            <p style="margin-bottom:0;">GenerationOptions</p>
          </td>
          <td data-label="Properties" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e31 ">
            <ul>
              <li>
                <strong class="uicontrol">DownloadFileFormat</strong>: Document type for
                download:&nbsp;All&nbsp;(default),&nbsp;Microsoft Word,&nbsp;Microsoft
                PowerPoint,&nbsp;PDF, or&nbsp;None.
              </li>
              <li>
                <strong class="uicontrol">AttachFileFormat</strong>: Document type for
                attachment:&nbsp;Microsoft Word&nbsp;(default),&nbsp;Microsoft
                PowerPoint,&nbsp;PDF,&nbsp;Word, PDF,&nbsp;PowerPoint, PDF,
                or&nbsp;None.
              </li>
              <li>
                <strong class="uicontrol">DocumentViewer</strong>: Preview
                format:&nbsp;PDF&nbsp;(default)&nbsp;or&nbsp;None. A value of&nbsp;None
                (case-sensitive)&nbsp;indicates that you can't preview the document.
              </li>
              <li>
                <strong class="uicontrol">DocumentTitle</strong>:&nbsp;Optional titles for the
                generated documents. Document Title overwrites the file name and the
                system shows the title in the document preview.<p>By using commas to
                  separate document titles, you can create different document titles for
                  the .docx or .pptx documents that you generate.</p>
              </li>
              <li>
                <strong class="uicontrol">DocGenerationMechanism</strong>: Read-only and selected
                as&nbsp;ClientSide. If you customize the Omniscript, you can make the
                generation options selectable.
              </li>
              <li><strong class="uicontrol">Insert Space for Repeating Content Tokens</strong>: Specifies whether the
                repeating content token's output is separated with spaces in a generated
                document.</li>

              <li><strong class="uicontrol">Keep Intermediate</strong>: [Optional] Specifies whether
                intermediate DOCX or PPTX files generated for PDF conversion are
                retained. When both attachFileFormat and downloadFileFormat are set to
                pdf, setting keep-intermediate=false triggers the system to delete the
                intermediate file after conversion, reducing storage usage. Supports
                singleDocxLwc, singleWebLwc, and multiDocxLwc OmniScripts through the
                LWCs ClmOsDocxGenerateDocument, ClmOsWebGenerateDocument, and
                ClmOsMultiDocxGenerateDocument. By default, keep-intermediate is set to
                true, maintaining existing behavior.</li>

              <li><strong class="uicontrol">documentGenerationFontSource </strong>- Specifies the
                source of the font used for rendering values during document generation.
                Possible values include Rich Text Editor Font, Document Font. The default
                value is Rich Text Editor Font. Rich Text Editor Font uses the font
                defined in the rich text field data, while Document Font uses the font
                defined in the document template.</li>
            </ul>
          </td>
        </tr>
        <tr class="">
          <td data-label="Omniscript Step" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e26 ">
            <p style="margin-bottom:0;">Set Generation Options</p>
          </td>
          <td data-label="Properties" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e31 ">
            <p>The system maps the values that you defined in the Generation Options step
              to the corresponding variables.</p>
            <p style="margin-bottom:0;">The step selects the <code>attachFileFormat</code>,
              <code>downloadFileFormat</code>, <code>documentViewer</code>,
              <code>pdfGenerationSource</code>,
              <code>documentGenerationFontSource</code>, <code>
                           insertSpaceforRepeatingContentTokens</code>,
              <code>documentTitle</code>, and
              <code>docGenerationMechanism</code> values that are to be passed to
              the Generate Document step.
            </p>
          </td>
        </tr>
        <tr class="">
          <td data-label="Omniscript Step" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e26 ">
            <p style="margin-bottom:0;">Generate Document</p>
          </td>
          <td data-label="Properties" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e31 ">
            <p>Generates the document with the option to send an email with the generated
              document attached.</p>
            <p>The generation process uses the
              <strong class="uicontrol">clmOsMultiDocxGenerateDocument</strong> LWC component , which uses
              JavaScript to invoke Apex classes for document generation.
            </p>
            <p>Pass these parameters to the LWC:</p>
            <ul>
              <li>
                <strong class="uicontrol">context-id</strong>: [Required] SObjectId, such as QuoteId, OpportunityId, OrderId, or ContractID. If context-id is null, the file looks for context-id in the data JSON of the Omniscript, which is set in the Set Values step.
              </li>

              <li>
                <strong class="uicontrol">selected-template</strong>: [Required] Passes the selected template. This parameter accepts the JSON format of the selected template. For capturing selectedTemplate details, see clmSelectableItems Lightning Web Component. Example JSON node: <code>{"Name": "TestGouse", "VersionNumber": 1, "DocumentGenerationMechanism": "ClientSide", "TemplateType": "MicrosoftWord", "Id": "2dtWU000000NUqDYAW", "Select": true}</code>
              </li>

              <li>
                <strong class="uicontrol">debug</strong>: [Optional] Displays the debug statement for the template query when turned on.
              </li>

              <li>
                <strong class="uicontrol">document-title</strong>: [Optional] Overrides the default document name of your document.
              </li>

              <li>
                <strong class="uicontrol">keep-intermediate</strong>: [Optional] Specifies whether intermediate DOCX or PPTX files generated for PDF conversion are retained. When both attachFileFormat and downloadFileFormat are set to pdf and keep-intermediate is false, the system deletes the intermediate file after conversion, which helps reduce storage usage. This parameter applies to singleDocxLwc, singleWebLwc, and multiDocxLwc Omniscripts through the LWCs ClmOsDocxGenerateDocument, ClmOsWebGenerateDocument, and ClmOsMultiDocxGenerateDocument. By default, keep-intermediate is true, which preserves existing behavior.
              </li>

              <li>
                <strong class="uicontrol">show-delete-icon</strong>: [Optional] The default value is true. If true, the delete icon appears in the document preview after the document is generated. If false, the delete icon doesn't appear in the document preview after the document is generated.
              </li>

              <li>
                <strong class="uicontrol">show-download-guidance</strong>: [Optional] The default value is true. If true, the message "For a seamless preview experience, use the Download button instead of the download icon to open your file." appears in the document preview after the document is generated. If false, the message doesn't appear in the document preview after the document is generated.
              </li>

            </ul>
          </td>
        </tr>
        <tr class="">
          <td data-label="Omniscript Step" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e26 ">
            <p style="margin-bottom:0;">GenerateMergeDocument</p>
          </td>
          <td data-label="Properties" class="slds-cell-wrap" style="vertical-align:top;" headers="d9167e31 ">
            <p>Combines multiple .pdf documents into a single .pdf document. The merge
              process uses the <strong class="uicontrol">clmOsGeneratePdfMergeDocument</strong> LWC
              component.</p>
            <p>To merge PDFs with <strong class="uicontrol">clmOsGeneratePdfMergeDocument</strong>, set
              these values in the Set Values step:</p>
            <ul>
              <li>
                <strong class="uicontrol">attachFileFormat</strong>:&nbsp;File format for the
                attachment. Enter <code>pdf</code> (case-sensitive).
              </li>

              <li>
                <strong class="uicontrol">documentViewer</strong>:&nbsp;Preview format. Enter
                <code>PDF</code> (case-sensitive).
              </li>

            </ul>
            <p>Pass these parameters to the LWC.</p>
            <ul>
              <li>
                <strong class="uicontrol">context-id</strong>:&nbsp;Salesforce record ID of the
                object that the final merged PDF is attached to. For example,
                <code>001Dl000018GQLAIA4</code>.
              </li>

              <li>
                <strong class="uicontrol">pdf-content-version-ids</strong>:&nbsp;Array of
                ContentVersion IDs of the PDFs to merge. For example,
                <code>["068Dl0000029lFJIAY", "068Dl0000029lFOIAY"]</code>.
              </li>

            </ul>
            <p style="margin-bottom:0;">You can merge up to 10 PDFs at a time, and the output PDF can be up to 25
              MB. If your org has a Public Sector Add-On license, you can merge PDF files
              up to 300 MB.</p>
          </td>
        </tr>
      </tbody>
    </table>