PDF Form Field Name Guidelines for SignaturePointSet
This section outlines the naming logic when the Signature, Date, and Initials fields are
selected as a value in the Type element within a
SignaturePointSet>SignaturePoint container with either Dynamic,
Static, or Embedded PDF documents.
<FillableFieldSet/> container in the response file when no ID
(for example: (RembrandID, SignerID, '*') is specified for Fillable Fields or Fillable
Checkboxes.Initials
Type element = "Initials" the FieldName
format consists of the following naming convention:
SS+TAG{"tagName": "Enter FieldName", "type": "Initials", "role": {"type": "Borrower", "num": 1}, "required": true}For example: SS+TAG{"tagName": "INI_Borrower_1_MyIniSignerID_true_1", "type":
"Initials", "role": {"type": "Borrower", "num": 1}, "required":
true}
| SS+TAG | This is a required prepend to the name |
| "tagName": "Enter FieldName", : | The FieldName value is created using
specific Expere logic to create a unique value. For example, in
the value "INI_Borrower_1_MyIniSignerID_true_1"
Note: the "tagName" value must be
unique. |
| "type": "Initials", : | "Initials" is the value used with the Type
element. |
| "role": {"type": "Borrower", : | |
| "num": | Set to the integer, starting with 1, for the corresponding responsible party. Expere will assign the integer sequentially to each unique party. if signer is identified with wildcard; it will get assigned to the first non-wildcard / non-null signers. See Additional "num" notes for more information. |
| "required": true} : | The "true" or "false" value is extracted from the
SignatureRequired element. |
<r:Id>MyIniSignerID</r:Id>
<r:SignerEmail>sigInifieldemail@email.com</r:SignerEmail>
<r:Description>Borrower</r:Description>
<r:SignaturePoint>
<r:IncludeDate>true</r:IncludeDate>
<r:PageNumber>1</r:PageNumber>
<r:PageOrder>1</r:PageOrder>
<r:Height>36.0</r:Height>
<r:Width>72.0</r:Width>
<r:SignatureText>INI_Name</r:SignatureText>
<r:XCoordinate>307.0</r:XCoordinate>
<r:YCoordinate>412.12</r:YCoordinate>
<r:Type>Initials</r:Type>
<r:FieldName>SS+TAG{"tagName": "INI_Borrower_1_MyIniSignerID_true_1", "type": "Initials", "role": {"type": "Borrower", "num": 1}, "required": true}</r:FieldName>
<r:Sequencing>5</r:Sequencing>
<r:SignatureRequired>false</r:SignatureRequired>
</r:SignaturePoint>Signature
Type element = "Signature" the FieldName
format consists of the following naming convention:
SS+TAG{"tagName": "Enter FieldName", "type": "Signature", "role": {"type": "Borrower", "num": 1}, "required": true}For example: SS+TAG{"tagName": "MySignerID", "type": "SIGNATURE", "role":
{"type": "Borrower", "num": 1}, "required": true}
| SS+TAG | This is a required prepend to the name |
| "tagName": "Enter FieldName", : | The FieldName value is created using
specific Expere logic to create a unique value. For example, in
the value "SIG_Borrower_1_MySignerID_true_1"
Note: the "tagName" value must be
unique. |
| "type": "Signature", : | "Signature" is the value used with the Type
element. |
| "role": {"type": "Borrower", : | |
| "num": | Set to the integer, starting with 1, for the corresponding responsible party. Expere will assign the integer sequentially to each unique party. if signer is identified with wildcard; it will get assigned to the first non-wildcard / non-null signers. See Additional "num" notes for more information. |
| "required": true} : | The "true" or "false" value is extracted from the
SignatureRequired element. |
<r:Id>MySignerID</r:Id>
<r:SignerEmail>MySignerEmail@email.com</r:SignerEmail>
<r:Description>Borrower, Borrower</r:Description>
<r:SignaturePoint>
<r:IncludeDate>false</r:IncludeDate>
<r:PageNumber>1</r:PageNumber>
<r:PageOrder>1</r:PageOrder>
<r:Height>36.0</r:Height>
<r:Width>72.0</r:Width>
<r:SignatureText>MySignerName</r:SignatureText>
<r:XCoordinate>307.0</r:XCoordinate>
<r:YCoordinate>412.12</r:YCoordinate>
<r:Type>Signature</r:Type>
r:FieldName>SS+TAG{"tagName": "SIG_Borrower_1_MySignerID_true_1", "type": "SIGNATURE", "role": {"type": "Borrower", "num": 2}, "required": true}</r:FieldName>
<r:Sequencing>5</r:Sequencing>
<r:SignatureRequired>true</r:SignatureRequired>
</r:SignaturePoint>Date
/Txn/EOriginalSSPlusUseManualDateInd=1.Type element = "Date" the FieldName format
consists of the following naming convention:
SS+TAG{"tagName": "Enter SignerIdentifier", "type": "AUTO_DATE", "role": {"type": "Borrower", "num": 1}, "required": true, "appearance": {"format": {"formatType": "DATE", "value": "MM/dd/yyyy"}}}For example: SS+TAG{"tagName": "INI_Borrower_1_MyIniSignerID_true_1", "type":
"AUTO_DATE", "role": {"type": "Borrower", "num": 1}, "required": true,
"appearance": {"format": {"formatType": "DATE", "value":
"MM/dd/yyyy"}}}
EOriginalSSPlusUseManualDateInd =1 and
Type element = "Date" the FieldName format
consists of the following naming convention:
SS+TAG{"tagName": "Enter FieldName", "type": "DATE", "role": {"type": "Borrower", "num": 1}, "required": true, "appearance": {"format": {"formatType": "DATE", "value": "MM/dd/yyyy"}}}For example: SS+TAG{"tagName": "INI_Borrower_1_MyIniSignerID_true_1", "type":
"DATE", "role": {"type": "Borrower", "num": 1}, "required": true, "appearance":
{"format": {"formatType": "DATE", "value": "MM/dd/yyyy"}}}
| SS+TAG | this is a required prepend to the name |
| "tagName": "Enter FieldName", : | The FieldName value is created using
specific Expere logic to create a unique value. For example, in
the value "SIG_Borrower_1_MySignerID_true_1_eSigDate"
Note: the "tagName" value must be
unique. |
| "type": "AUTO_DATE", : | "AUTO_DATE" is the value used when the Type
element is "Date" and
/Txn/EOriginalSSPlusUseManualDateInd does
not = 1 or XPath is not present or passed in. |
| "type": "DATE", : | "DATE" is the value used when the Type
element is "Date" and
/Txn/EOriginalSSPlusUseManualDateInd =
1. |
| "role": {"type": "Borrower", : | |
| "num": | Set to the integer, starting with 1, for the corresponding responsible party. Expere will assign the integer sequentially to each unique party. if signer is identified with wildcard; it will get assigned to the first non-wildcard / non-null signers. See Additional "num" notes for more information. |
| "required": true} : | The "true" or "false" value is extracted from the
SignatureRequired element. |
| "appearance": | {"format": {"formatType": "Date", "value": "MM/dd/yyyy"}; will specify the date value in an "MM/dd/yyyy" format. |
<r:Id>MySignerID</r:Id>
<r:SignerEmail>MySignerID@email.com</r:SignerEmail>
<r:Description>Borrower, Borrower</r:Description>
<r:SignaturePoint>
<r:IncludeDate>false</r:IncludeDate>
<r:PageNumber>1</r:PageNumber>
<r:PageOrder>1</r:PageOrder>
<r:Height>36.0</r:Height>
<r:Width>72.0</r:Width>
<r:SignatureText>SigFieldSignerName</r:SignatureText>
<r:XCoordinate>307.0</r:XCoordinate>
<r:YCoordinate>412.12</r:YCoordinate><r:Type>Date</r:Type>
<r:FieldName>SS+TAG{"tagName": "SIG_Borrower_1_MySignerID_true_1_eSigDate", "type": "Date", "role": {"type": "Borrower", "num": 1}, "required": true, "appearance": {"format": {"formatType": "DATE", "value": "MM/dd/yyyy"}}}</r:FieldName>
<r:Sequencing>5</r:Sequencing>
<r:SignatureRequired>false</r:SignatureRequired>
</r:SignaturePoint>