RightSignature Tags provide an efficient way to customize signer fields in document files (DOCX or PDF). This functionality is integral for ensuring that clients can interact with and sign documents digitally, with the capability to designate required and optional fields based on the signing hierarchy.
RightSignature Format
Each tag is made up of three arguments, first argument, second argument and third argument. Here is an example of a possible tag you could use:
[ s:a:r ]
FIRST ARGUMENT
This argument describes the type of field this tag will be.
- s = signature
- c = check box
- d = date field
- i = initials field
- t = text field
SECOND ARGUMENT
This argument designates to whom the field is assigned using A through Z in alphabetical order to correspond to the signer.
- a = first document signer
- b = second document signer
- c = third document signer
- etc
THIRD ARGUMENT
This argument designates the field as either required or optional. Note that signatures are always required and cannot be set as optional.
- o = optional
- r = required
IMPORTANT NOTES:
- Spaces and underscores are ignored between the square brackets. Signatures are always required.
- After you've added these fields to your documents, it's imperative to make the font white, or the same color as the background color of the document. This way, the Right Signature tags will not show on the signed document, only the signatures.
- To make the signing space larger for your clients, you may make the font larger or add spaces in between the brackets. Here's an example:
-
[ s:a:r ]
-
RightSignature Code
The code configuration allows for seamless document tagging and integration with advanced features such as merging. Once tagged, documents are uploaded into the system to be used for digital signing.
Code Implementation Steps:
-
Upload Document:
- Standard documents: Use the Upload Document option.
- Documents with merge tags: Use the Advanced Merge Document option.
-
Library Settings:
- Navigate to: Settings > Library Setup > ClientPoint Files.
- Select the desired document and click Edit.
-
Code Syntax:
- Add the appropriate JSON configuration to the DocuSign area.
- Each signer (e.g., Customer, Co-Signer, Owner) must have separate sections for their signing tabs and date-signed tabs.
-
Signer Configurations:
- One Signer: Defines fields for one document signer.
- Two Signers: Adds a second signer's configurations.
- Three Signers: Incorporates a third signer while maintaining clear structure.
ONE SIGNER:
{
"Customer": {
"tabs": {
"signHereTabs":
[
{
"anchorString": "OwnerSignBBP1",
"documentId": "%%documentId%%"
}
],
"dateSignedTabs":
[
{
"anchorString": "OwnerDateBBP1",
"documentId": "%%documentId%%"
}
]
}
}
}
{
"Customer": {
"tabs": {
"signHereTabs":
[
{
"anchorString": "OwnerSignBBP1",
"documentId": "%%documentId%%"
}
],
"dateSignedTabs":
[
{
"anchorString": "OwnerDateBBP1",
"documentId": "%%documentId%%"
}
]
}
},
"Owner": {
"tabs": {
"signHereTabs":
[
{
"anchorString": "OwnerSignBBP1",
"documentId": "%%documentId%%"
}
],
"dateSignedTabs":
[
{
"anchorString": "OwnerDateBBP1",
"documentId": "%%documentId%%"
}
]
}
}
}
{
"Customer": {
"tabs": {
"signHereTabs":
[
{
"anchorString": "OwnerSignBBP1",
"documentId": "%%documentId%%"
}
],
"dateSignedTabs":
[
{
"anchorString": "OwnerDateBBP1",
"documentId": "%%documentId%%"
}
]
}
},
"Co-Signer": {
"tabs": {
"signHereTabs":
[
{
"anchorString": "OwnerSignBBP1",
"documentId": "%%documentId%%"
}
],
"dateSignedTabs":
[
{
"anchorString": "OwnerDateBBP1",
"documentId": "%%documentId%%"
}
]
}
},
"Owner": {
"tabs": {
"signHereTabs":
[
{
"anchorString": "OwnerSignBBP1",
"documentId": "%%documentId%%"
}
],
"dateSignedTabs":
[
{
"anchorString": "OwnerDateBBP1",
"documentId": "%%documentId%%"
}
]
}
}
}
Conclusion
The RightSignature Tags and Code Integration enhance document customization and signing processes, offering a structured way to define and assign digital signing fields. The flexibility of the tag system ensures adaptability to various document requirements, while the JSON-based code streamlines integration for single or multi-signer scenarios.
By following the guidelines for tag usage and code implementation, users can create professional and efficient document workflows that simplify client interactions and maintain a polished digital experience. For additional assistance, reach out to support@clientpoint.net.