Interactive E-Sign Documents

1. Creating Content and Input Elements

To start creating content in Documill Dynamo, open a document from the Home screen. To collect data in different formats like text, dates, or checkboxes, go to the Components tab on the left. Drag and drop the needed input elements into the main document body to build your content.

Inputing form elements to the document layout

Basic form elements are provided in the Components tab when creating Document layout. The components can be added to where the cursor is placed.

1. Text: Accepts basic text input and is versatile for fields such as Name, Email, or Phone Number. Users can specify the input type, including:

   • Email: For email addresses.

   • Tel: For telephone numbers.

   • Text: For general text fields.

   • Number: For numerical input (e.g., Age, Quantity), with validation for min/max values. Appears as a text box with up/down arrows.

   • Date: Used for selecting dates (e.g., Birthdate, Event date) with a calendar picker.

   • Time: For time input with time picker.

   • Week: To select a specific week through calendar interface.

   • Month: For selecting a specific month via a month picker.

   • Range: For numerical ranges with a defined range where users can select values between a minimum and maximum.

2. Number: Accepts numerical input for fields like Age, Price.

3. Date: To collect date value, e.g., birthday or contract signing date.

4. Checkbox: to collect Boolean value, true or false.

5. Rich Text Field (RTF): For multiline or formatted text entries.

6. Text Inline: Collects small text inputs within a sentence, ideal for fields like initials, short names, or brief descriptions.

2. Setting Bound Values

Each input element must be assigned a unique Bound Value, which acts as a variable to capture the data entered by users. This Bound Value can then be referenced throughout the document or within the template workflow for processing or display.
Additionally, you can configure a Placeholder for each input element, providing users with a hint or example of what data should be entered in the field.

Bound Values must be unique and should begin with the prefix dynFields… For example, dynFields.fullname

Bound and Placeholder Preview

3. Enabling Responsive view and Allow Input

1. Go to Settings.

2. Navigate to the Signing tab.

3. Toggle Responsive View to ON. Once enabled, the Allow Input option will appear.

4. Toggle Allow Input to ON.

Responsive View and Allow Input Preview

4. Print Emulation

This option in the Document tab adjusts the document layout to match the printed page dimensions.

• When enabled, this feature displays the document as it would appear on a printed page, which may require horizontal scrolling on smaller screens to view the entire document.

• When disabled, the document automatically adjusts to fit the screen size, providing a responsive view that eliminates horizontal scrolling. This ensures the entire document is fully visible and accessible on any screen size, offering a better viewing experience during the review process.

Print Emulation Enabled tested on mobile screen	Print Emulation Disabled tested on mobile screen
It displays as it would in print size, which may require horizontal scrolling on smaller screens to view the full layout.	When Disabled - The document fits the screen size, eliminating horizontal scrolling

6. Write back Data back to Salesforce

To ensure that data saved back to Salesforce after document signing, follow these steps to configure the workflow and add the necessary functions.

1. Access the main flow, select step ´Custom Data´ then edit ´Load Data´ and use addMapEntry command to map dynamic field values to specific identifiers.

Main Flow Configuration

2. From the Home tab, access the ShareEnd subflows and select step ‘Share end’.

   

3. Find the correct When command. For E-signing workflow, the document status signed should be used.

4. Choose update command. In the type box, enter the API Name of the Salesforce object you want to update (e.g., Opportunity or Account).

5. Add child field commands. The first field command should contain the record ID of the Salesforce record to update. Add subsequent field commands for each field you intend to update, where name should contain the API Name of the target field in Salesforce and value is the configured input form value. For example, dynFields.fullname. There can be as many field commands as needed.

Subflow ShareEnd Configuration

After clicking the Exit button post-document generation, the user's input updates the Description in Salesforce, enabling seamless real-time data transfer.