Understanding the CyberGrants Email Merge Field Extension
The CyberGrants Email Merge Field Extension is a standardized enhancement designed to enable dynamic insertion of custom field data into standard email events and eSignature documents. This functionality empowers customers to create more personalized and context-aware communications within the CyberGrants platform, supporting a more engaging and tailored experience for recipients.
By leveraging this extension, customers can dynamically populate email templates and eSignature forms using data fields from standard CyberGrants tables. This improves both operational efficiency and messaging relevance while ensuring consistency in communication.
Check out the video below to learn more!
Key features:
- Customers can insert custom merge fields into email events or eSignature documents, with the number of supported fields depending on complexity.
- The extension supports up to ten simple merge fields (such as pulling a date from a field) or up to five complex merge fields (such as concatenated values or calculated sums). Once configured, these fields can be reused across multiple email or eSignature templates.
- The merge field values can be sourced from the Organization, Request, or EG Request tables (EG Request fields can only be used with email events, as they are not applicable for eSignature templates).
- Supported custom field types include Date, Yes/No, Number, Currency, Paragraph, Text, Multi-Select, and Single-Select fields.
- Custom fields are displayed as-is, with no additional formatting, logic, or conditional behavior applied.
- Merge fields may be reused across email and eSignature communications, but each use is counted separately.
Limitations and considerations:
- Only direct fields from standard tables can be used; custom table fields or computed logic (e.g., sums, concatenations) are not supported.
- Each merge field included in both a standard email and an eSignature document counts as two separate field implementations.
- UI modifications or conditional field logic are out of scope.
- Customers must fully participate in User Acceptance Testing (UAT) before functionality can be promoted to production.
- Approved Functional Requirements cannot be modified without affecting the timeline and potentially incurring costs.
To learn more about this extension, please review the following articles. For assistance with acquiring this extension, please reach out to your assigned Implementation team's Project Manager.
What do you need help with?
