Field Mappings and Naming

When a requester fills out a form and submits it, their answers need to end up in the right places on the generated contract. Without field mappings, someone would have to manually copy the governing law, effective date, and party name from the form submission into the contract record. Mappings automate this.

Field mappings connect form fields to contract properties. Naming tokens auto-generate entry titles, contract names, and file names from form data. Together, they eliminate the manual data entry between form submission and contract creation.

Each form field can be linked to a contract property. When the form is submitted and a contract is generated, the field’s value is written to that contract property automatically.

For example:

• Form field “Governing Law” (dropdown) → Contract property “Governing Law”
• Form field “Effective Date” (date) → Contract property “Effective Date”
• Form field “Contract Value” (number) → Contract property “Contract Value”

In the field editor, each field has a Contract property selector. Click it to see a list of available contract properties. Select the property this field should map to.

The mapping is per-field, not per-action. If your form has multiple actions that generate different contract types, the same field mapping applies to all generated contracts.

Party fields have additional mapping capabilities beyond standard contract properties. When a party field is submitted:

1. The party record is created or linked in Pactly (either a new party is created or an existing one is matched)
2. The party is assigned roles on the generated contract (e.g., counterparty, signatory, our representative)
3. Party attributes (custom fields on the party) can be mapped to contract properties through the party mapping configuration

Party mappings are configured within the party field settings, not through the standard contract property selector.

For form sequences only. Reverse mappings pre-fill form fields with values from an existing contract’s properties. This is useful when a later form in a sequence needs to display or confirm data that was set by an earlier form.

Enable “Use reverse contract property” on a field and select which property keys to pull from. The field will be pre-populated with the current value of that contract property.

Forms can auto-generate three types of names using a token-based system:

In the form builder’s Settings tab, you’ll find three naming token fields under the naming section. Each field shows a sequence of tokens that get joined together to produce the final name.

Click between tokens to insert new ones. Drag tokens to reorder them. Each naming field supports up to 60 tokens.

There are four types of tokens:

Value tokens insert a predefined value:

• Submitter Email - The email address of the person who filled the form
• Form Name - The form’s title
• Date - The creation date in YYYYMMDD format
• Template Name - The name of the template used (contract name and file name only)
• Contract Reference - The auto-generated reference number (contract name and file name only)
• Category - The contract category label (contract name and file name only)
• Category Abbreviation - The short form of the category (contract name and file name only)

Input tokens insert fixed text that you type. Useful for separators (like ” - ” or ” _ ”) or fixed prefixes.

Field tokens insert the value of a form field. When the token is evaluated, it’s replaced with whatever the requester entered. Works with text, list, number, and party fields.

Party block tokens combine multiple attributes from a party field with a configurable separator. For example, a party block combining “firstName” + “lastName” with a space separator produces “John Doe.”

Not all tokens are available for all naming types:

Entry titles are generated at submission time, before a contract exists. That’s why template, reference, and category tokens aren’t available for entry titles.

When tokens are evaluated:

1. Each token is replaced with its value
2. All values are joined together (no separator between tokens, so use Input tokens for separators)
3. Consecutive separators (hyphen, underscore, space) are collapsed to one
4. Leading and trailing separators are removed
5. The result is truncated to 256 characters

Below the file name field, a “Copy from Contract” button copies the contract name token sequence to the file name field. This saves time when you want the file name to match the contract name.

The form builder checks for mapping issues and shows a Review Mapping Errors button when problems are found. Common errors include:

• A required contract property has no field mapped to it
• A field is mapped to a property that doesn’t exist on the target template
• A party field has no roles assigned

Fix these before sharing the form to ensure contracts are generated with complete data.

• Creating a Form
• Form Actions
• Field Types Reference
• Contract Properties