Merge Fields:
For CyberGrants to detect that there are merge fields within an uploaded template, these templates must indicate which data points are merge fields. The way these are indicated may be variable by the document format (.docx or .pdf).
- For Grantmakers using .docx formats, merge fields should be indicated by wrapping the appropriate text in curly brackets: {}
- For grantmakers using .pdf formats, merge fields can be indicated by utilizing form fields via a PDF editor or Adobe Acrobat Sign’s advanced functionality.
NOTE: It is recommended to adjust the font color of the DocuSign merge fields to match the background color to ensure the merge fields are not visible beneath the signature and date fields.
Signer Fields:
For the eSignature provider to correctly capture signatures, each template must contain fields for
- the signature and
- the date that the signature was captured.
These are not merge fields within CyberGrants, but content filled in by the provider and returned in the executed document. Expected field formats for signer fields are listed below.
- It is recommended that the font color of these merge fields be changed to match the background color of the document so they are not visible beneath the signature and date.
- The maximum number of allowed signatures is 12. The minimum number of required signatures is 1. Templates can be built to accommodate a variable number of signers.
NOTE: The bolded fields below are required for proposal types utilizing E-Signature.
Field Name:
|
Purpose:
|
| Ready to send for eSignature | Determine when a request is ready for a document to be sent for signature. |
| Re-Send LOA Document | Resend a document that’s already been sent. |
|
eSignature Document Status
eSignature Document Sent Date
eSignature Document Status Date
| Track the status of sent documents. |
|
eSignature Current Signer Name
eSignature Current Signer Email
eSignature Document Signed Date
| Track the most recent signer and when they signed. |
| eSignature Current Signer Order | Track signer order. |
| eSignature template to send | Choose which template to use (if multiple are mapped to the proposal type). |
|
eSignature Signer 1 Name
eSignature Signer 1 Email
eSignature Signer 2 Name
eSignature Signer 2 Email
eSignature Signer 3 Name
eSignature Signer 3 Email
…repeat…
eSignature Signer 12 Name
eSignature Signer 12 Email
| Record who needs to sign and their information. |
| eSignature Completed LOA | Capture fully executed document.
(This field must be included within the proposal type or the process will fail.) |
What else do you need help with?
Not what you're looking for? Navigate to Understanding eSignature for Grant Programs
Looking for training?
Explore this feature at your own pace - access training video content or watch a recorded webinar by clicking the link below.
