- 08 Oct 2024
- 1 Minute to read
- DarkLight
- PDF
Custom Fields
- Updated on 08 Oct 2024
- 1 Minute to read
- DarkLight
- PDF
A Custom Field is one that, at the time of signing, is automatically populated with data that is specific to the signer. For instance, a signer might have an Agent Number, and that number may need to appear in the final document next to their signature. By using a custom field, the signer can specify their Agent Number, and that number will automatically appear in any other field that has been configured to receive it.
The Custom Fields page enables you to manage the custom fields in your account. However, this functionality is available only if custom fields are enabled at the account level.
Users in your account can populate the custom fields with the appropriate information from their account profiles. To update the information that will appear in a transaction, see configuring a custom field.
Creating a Custom Field
To create a custom field:
From the top menu, click Admin > Custom Fields.
On the Custom Fields page, click New Field. This opens the Create New Custom Field dialog box.
Specify the following items, and then click Save.
Field Parameters
The following fields are displayed:
Field ID: This is the field's identifier in the database. Senders will not see this ID and there can be no spaces in this field.
Default Value: This will be the field's default value. This value is optional and can be changed by the Signer in their account profile.
Required: Flag that indicates if the custom field will be required for users when setting up their account profiles.
Field Localization
The following fields are displayed:
Language: Select a supported language.
Field Name: Specify a Field Name for the selected language. This is a required field. This is the name of the field as your users see it in their account profiles and on transactions in which they participate.
Description: Optionally provide a description of the selected language.
This tip is for accounts that support multiple languages. As a best practice, every custom field you need should be replicated for every language supported in your account. The system will only display the custom field in the language selected by the active user. If a custom field is not mapped to a language, it will default to English, regardless of the language selected by the active user.