Loading
Agentforce Field Service and Operations
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Document Builder Standard Components

          Document Builder Standard Components

          Here’s a list of standard components available for Document Builder, with descriptions.

          Required Editions

          Available in: Lightning Experience.
          The Field Service core features, managed package, and mobile app are available in Enterprise, Unlimited, and Developer Editions.

          Document Builder has these standard components. Set the conditional visibility of all components and choose to show them only under specific criteria. For example, if the parent record is Work Order, and the related object is Work Order Line Item, you can choose to show a related record table only if the work order’s work type is Break-Fix. When you create a community site, you can use the service document feature only with the Help Center, Build Your Own (Aura), Customer Service, and Customer Account Portal templates.

          Component Details
          Grid

          The grid divides the canvas into columns. To divide each section into multiple columns and control the width of each column, add the Grid component to the header, body, or footer. To use, drag the Grid component onto the canvas. After you do, you see the Grid settings in the Document Settings menu on the right. Here you can change the number of columns (up to 12), the width of each column, and the space padding between the columns.

          If you set the conditional visibility rules to hide the grid, the grid and all fields within the grid are hidden. If the grid is visible, you can still set conditional visibility rules for individual fields within the grid. If you have a conditional visibility rule to hide a field within a grid, it’s hidden.

          Page Break Page breaks control the pagination of your service document and organize your content into sections.
          Page Numbers When added to the header or footer, repeats on all pages of the document. After you add it to the canvas, the Document Settings menu shows the Page Numbers Settings, where you can change the format and alignment.
          Related Record Table

          Related record tables show records from child objects related to the service document’s template object. For example, if the template object is Work Order, the related record table shows records from the Work Order related objects, such as Work Order Line Items, Products Consumed, Expenses, and Time Sheet Entries. When the Related Record Table component is added to the canvas, you can use the component settings panel on the right to configure table details, including:

          • Parent record: This field defaults to the Template object, for example, Service Appointment.
          • Related entity: This field lets you select which child object’s record you want to show in the table.
          • Related record fields: Add a maximum of 10 related record fields (columns) to the table.
          • Show related records table when the list is empty: This setting is deselected by default and hides related lists that have no records. When the setting is selected, related lists that have no records are shown with only the column headers and no records.
          • Set equal width for columns: By default, column widths are set based on the size of the field label. (Fields with larger labels appear with wider column widths). When the setting is selected, the column widths are evenly distributed across all fields.
          • Sort field and sort order: Sort records within the related list. Use these fields to specify which field to use to determine sort order and whether sorting occurs in ascending or descending order.

          Geolocation and Text Area (Long) field types aren't supported.

          Signature

          The signature component captures signatures from customers, partners, and mobile workers on service documents through both the app or web. Define the number of signatures needed by adding signature components to the canvas. You can also adjust the signature breadth and height. Reorder, include, or exclude these fields by specifying settings in the component settings panel.

          Because these fields are standard fields on a standard object, they’re translated in the user’s language. You can customize the labels related to the Digital Signature object and rename them to suit your branding and business needs. If you don’t change the labels of the object or fields, Salesforce translates the label values for you. If you change labels, or if you want to modify the standard translation provided by Salesforce, you can translate those new labels.

          Image Embeds images into your service document. Add images to your image library. Then, from the document component panel, select your image, and then use the canvas to add image descriptions and include alt text for accessibility. Images must adhere to the Salesforce guidelines for file size, found in Salesforce CRM Content Limits.
          Image Gallery

          The image gallery shows all images associated with the object from which you create your service document. All images added as files to the template object are shown in this component. While you can dictate the number of images to show per row, you can’t modify the total number of images. Images in a row have the same size and resolution. You can include captions for each image.

          Rich Text

          Add custom text with styling and formatting to your documents. To represent information such as help text, section headers, disclaimers, add custom labels. Custom labels are translatable, so using this setting in a rich text component lets you translate the content without having to build multiple templates for each language your company supports.

          To personalize your service documents, use embedded expressions in rich text components. Drag a rich text component onto the canvas. Optionally, add static text to give context for the embedded field. To embed the field into the rich text component use the following syntax: {!Record.fieldname} or {!Record.Objectname.fieldname}. For example, to embed a phone number for an account, the syntax is {!Record.Account.phone}. For custom labels the format is {!$Label.labelName}. Save the template, and then test it on the document preview.

          Address, Geolocation, Compound Fields, Picklist, Multi-select Picklist, Text Area (Long), Text Area (Rich), and Text (Encrypted) aren’t supported for embedded expressions in rich text.

           
          Loading
          Salesforce Help | Article