Overview
Templates are the agreement framework that LinkSquares Finalize Administrators build out to facilitate and expedite the creation process. Finalize Administrators are responsible for creating and managing the templates within Finalize.
Templates are pre-approved, customized workflows that empower self-service drafting. Once a template has been created, users can quickly generate new agreements using the template.
The templates that were configured within Finalize will also be available within the LinkSquares Finalize integration in Salesforce. Salesforce Administrators can configure templates to auto-populate with Salesforce data during the Salesforce Finalize drafting process.
Note: To use templates with Single-selection tokens in Salesforce, you must be on version 2.4 or later of the Salesforce Finalize package.
Process
The template configuration process consists of the following areas:
- Configuring Root Objects
- Agreement Name Mapping
- Mapping to Salesforce Fields
- Field Editing Restrictions
- Sorting and Filtering on Tables
- Parent-Child Relationships
- Template Display Settings
To begin configuring a Salesforce template, navigate to the Template Configuration tab of Salesforce Finalize.
Click Configure for the relevant template.
Locate templates by name or description using the search bar.
Click the sorting icons on the Template Name or Description columns to adjust the order in which templates appear.
Configuring Root Objects
If the template has not already been configured within Salesforce Finalize, a root object must be created.
A root object is the Salesforce object on which the template is available for drafting (e.g., opportunity, account).
If the template is available for drafting on multiple Salesforce objects, configure a root object for each Salesforce object.
Click + Root Object.
Select the root object on which the template resides.
Click Save once complete.
The root object will appear under the Added root objects section.
To remove a root object, click Remove Root Object. A modal will appear to confirm you would like to remove the root object, click Remove.
The root object and all associated mappings will be deleted.
Now, the agreement detail fields and tokens for the template can be mapped to Salesforce fields within the root object(s).
Agreement Name Mapping
The agreement name can be mapped within templates. If the agreement name is mapped, it must be a Text Formula field with a text LinkSquares input type.
The recommended formula for mapping an agreement name depends on which root object the template is on. For example, a template with an opportunity root object could use the formula:
“Account.Name & "-" & "Template Contract Type" & "-" & TEXT (DATEVALUE (NOW ()))”
Using the Opportunity object as an example, create a text formula field in Salesforce on this object:
Check the syntax after inputting the formula:
In this example below, the formula would pull "Account Name - Master Service Agreement - Today's Date":
Note:
- In the above example, Template Contract Type is inserted as plain text to add the related template name to the Agreement Name formula field.
- The LinkSquares Input Type column outlines what field type the token or agreement detail question was given during template configuration within Finalize.
- The agreement name will be the first entry under the Agreement Details section.
Within the Opportunity, click the drop-down arrow on the agreement name field and select Edit.
Enter the formula field in the Salesforce field path:
Click Save once complete.
The Salesforce Field Path should display the designated Salesforce name field:
If the fields are set as editable during template configuration, Drafters will be able to edit the agreement name field when drafting a new agreement within Salesforce.
To learn more about setting fields as editable, reference the Field Editing Restrictions section of this article.
Mapping to Salesforce Fields
Next, map each agreement detail field and token to a Salesforce field.
These mappings are not required. If fields are left unmapped, the field will be blank during drafting workflows.
If fields are mapped, the field will be auto-populated with data during drafting workflows.
Note:
- The red asterisks indicate the agreement detail fields and tokens that were marked as required during the template creation process in the Finalize web app.
- Multiple-selection and Single-selection agreement detail fields and tokens as well as Clause tokens cannot be mapped within Salesforce. They must be manually configured within Finalize in the agreement creation flow.
- Dynamic Questions cannot be mapped to Salesforce fields.
The LinkSquares Input Type of the agreement detail field or token must match the data type of the Salesforce field it is mapped to. For example, if the agreement detail field is “What is the effective date of the agreement,” it should be mapped to a Salesforce field that represents a date.
Click the arrow to the right of the relevant field and select Edit.
If a mapping has already been configured, the option to remove the existing mapping is available.
Select the Salesforce field or field path for your values to map from.
Field paths can be configured to pull data from a Salesforce field that is not available at the root object level.
Selecting a field with a greater-than symbol (>) will drill into that object and allow data to be pulled from a related field.
For example, selecting Account > will drill into the account object and pull data from an associated field (e.g., account name, account ID, etc.).
Note: Field paths can be configured with up to three levels.
Click Save once complete.
Repeat this process for every agreement detail field and token that should be mapped to a Salesforce field.
The following table outlines the Salesforce field types to which the LinkSquares input types can be mapped.
| LinkSquares Input Type | Applicable Salesforce Fields and Field Paths | Non-applicable Salesforce Fields and Field Paths (Filter Out) |
| Text Field |
|
|
| Text Area | Same as above |
|
| Date |
|
All other fields |
| Clause |
Cannot be mapped in Salesforce. Must be configured in Finalize. |
Cannot be mapped in Salesforce. Must be configured in Finalize. |
| Multiple-Selection |
Cannot be mapped in Salesforce. Must be configured in Finalize. |
Cannot be mapped in Salesforce. Must be configured in Finalize. |
| Single-Selection |
Cannot be mapped in Salesforce. Must be configured in Finalize. |
Cannot be mapped in Salesforce. Must be configured in Finalize. |
| Number |
|
All other fields |
Field Editing Restrictions
Administrators can configure whether users can edit agreement detail fields and tokens during drafting workflows.
Field editing restrictions can be configured globally for the template or individually for each field.
To restrict users from editing all agreement detail fields and tokens that have been mapped during drafting workflows, click the Lock All Fields button.
To allow users to edit all agreement detail fields and tokens that have been mapped during drafting workflows, click the Unlock All Fields button.
This functionality is template-based and works for all root objects.
Note:
- Locking fields does not restrict the ability to map agreement detail fields or tokens to Salesforce data.
- This logic applies to all template types.
To restrict users from editing an individual agreement detail field or token that has been mapped during drafting, select Lock Field from the drop-down for that field after configuring a mapping.
If this field is currently locked, select Unlock Field from the drop-down to allow users to edit the field during drafting.
Sorting and Filtering on Tables
Templates for quotes or order forms may contain one or more tables with many fields in them. These tables can be sorted or filtered to exclusively show relevant products or line items.
Note: Sorting and filtering functionality only applies to templates with tables in them.
Sorting and filtering apply to a limited set of field types within these templates.
Field types that can be sorted or filtered include:
- ID
- Picklist
- Text
- Lookup
- Master-Detail
- TextArea
- URL
As such, the following fields are excluded:
- Date
- DateTime
- Time
- Checkbox
- Number
- Currency
Note: This list is not exhaustive. Any field type not on the previous list is excluded from sorting and filtering abilities.
To learn more about applying filters or sorts to a table during template configuration and configuring templates with tables in them, reference our article on Salesforce Finalize: Pricing Table Configuration.
Parent-to-Child Relationship
Parent-to-child relationships are used by pricing tables.
To learn more about pricing tables, reference our article on Salesforce Finalize: Pricing Table Configuration.
Click the Select Relationship button to configure a parent-to-child relationship.
Click the Edit Relationship button to update a parent-to-child configuration.
Template Display Settings
Control which templates are available on a given object using Template Display Settings.
The templates that are available on a given object are the templates from which users can draft agreements.
On the Template Display Settings tab, select an object record page from the drop-down (e.g., opportunity).
Enter the desired object record page to filter the available options.
Use the arrows between the Available Templates and Templates displayed on the X record page columns to move templates to and from the selected object record page.
The templates under the Templates displayed on the X record page column will appear on the selected object record page. The templates under the Available Templates column will not.
Use the search bar to locate a template by name.
Use the arrows to the right of the Templates displayed on the X record page column to arrange the order in which templates appear on the selected object record page.
To return to the main Template Configuration tab, click the hyperlinked Template Configuration at the upper left-hand corner.