Optional Add-On Module for the collaboration of documents between internal and external users/participants. This module utilizes E-Approval (Electronic Approval) and/or E-Signature (Electronic Signature) processing to support full online negotiation via a secure online portal.
DOCUMENT COLLABORATION & E-SIGNATURE
ENHANCEMENTS
ENHANCEMENT: Improved Formatting Support for Subtables in Document Templates
Reference #: 260127.1157.24340
We’ve improved how subtables behave during document generation to ensure they match the formatting defined in your templates. This enhancement resolves prior issues where subtables appeared with the wrong font, size, bolding, alignment, or margin placement.
- Subtables now inherit the font style, size, and bold formatting of the placeholder.
- Table headers will always display in bold for clarity.
- Subtables now respect page margins and no longer shift off‑center.
- Indentation behaves consistently based on surrounding content.
- When converting to PDF, all subtable formatting is fully preserved.
How will this affect users?
Merged documents will now display subtables exactly as configured—creating cleaner, more consistent, and professional‑looking output with no manual adjustments needed.
DOCUMENT COLLABORATION & E-SIGNATURE
RESOLUTIONS
RESOLUTION: Vendor/Client Name Truncated on Document Template Merge
Reference #: 260127.345.24080
We fixed an issue where Vendor/Client names longer than 30 characters did not fully appear when merging a document template into an Amendment. Previously, only the first 30 characters of the Vendor/Client name from the Contract Details table were included in the merged document.
This has been corrected, and the entire Vendor/Client name now successfully merges into templates as expected.
RESOLUTION: Amendment Clause Merge Numbering
Reference #: 260127.1157.22703
Some customers experienced an issue where amendment‑specific merge fields did not populate correctly when generating documents. In certain cases, the amendment number displayed in the document header would change unexpectedly when multiple placeholders were merged within the same document.
We’ve resolved the issue to ensure that:
- Amendment numbers remain stable and accurate throughout the document.
- Header placeholders no longer change unexpectedly during merges.
- Clause formatting is preserved consistently—especially when multiple placeholders must be replaced in a single document.
Documents will now reliably display the correct amendment number in all locations, and mergable clauses will behave as expected when tied to amendment line items.
RESOLUTION: Document Template Attachments Set to Lock PDF Not Printable
Reference #: 260127.345.24369
We’ve corrected an issue that prevented certain merged PDFs from being printed. When users selected Convert to PDF and Lock PDF on a document template’s attachment settings, the generated PDF could be downloaded but not printed.
The locking logic has now been updated so that PDFs created with these settings are printable as expected, while still maintaining their intended protections.
RESOLUTION: Users without External E-Sign Module Unable to Use IntelliSign
Reference #: 260127.345.24614
Some clients using Document Collaboration and IntelliSign—but not the External E‑Sign module—were incorrectly seeing a message indicating they were “out of free processes” and were unable to use IntelliSign.
A fix has been applied, and IntelliSign is now fully accessible and functioning as expected for these clients.
RESOLUTION: Document Merge Issues Using Request Task Details
Reference #: 260127.1157.22816
Some users were unable to successfully merge documents when their templates included fields from Request Task Details. In these cases, attempting to merge the document produced an error indicating an invalid Request ID.
In addition, templates that used Request Task Details inside mergeable clauses did not show an error—but the merged document would generate without pulling in any of the expected task information.
We've updated the logic that validates how Request Task Details are used within a template. This ensures the system correctly recognizes and connects the relevant task data before merging.
RESOLUTION: Mergeable Clause Content Not Matching Attached Clause
Reference #: 260127.1157.24751
Some customers experienced an issue where the content merged into a document template did not match the content of the attached mergeable clause. In some cases, header and footer content from the attached clause was inserted into the body of the document instead of remaining in the header or footer.
We updated the document‑merge behavior to correctly respect the formatting and placement of mergeable clauses.
RESOLUTION: Document Template Font Formatting Not Preserved During Merge
Reference #: 260127.1157.23327
We resolved an issue where the font type and formatting of a document template changed unexpectedly when the template was merged onto a record. This occurred specifically in areas containing mergeable placeholders, which caused the merged document to display a different font than the original template.
This behavior has now been corrected.
Document templates will retain their original font and formatting throughout the entire document, including all sections that use merge placeholders.
RESOLUTION: Missing Signatures on Finalized Landscape Documents in IntelliSign
Reference #: 260127.345.22434
During the signing workflow, users noticed that signatures appeared correctly while in progress. However, once the signing process was completed and finalized, the merged output failed to retain all participant signatures on landscape‑formatted documents. In certain environments, landscape documents also failed to finalize and appeared stuck “in process.” This impacted both PDF and Excel files that were formatted in landscape. Documents using portrait orientation were not affected.
We updated the handling of landscape documents within IntelliSign to properly recognize document orientation and maintain signature placement during the finalization step. The system now correctly preserves all participant signatures regardless of whether the file is in landscape or portrait format.
RESOLUTION: Extra Line Breaks and Formatting Issues in Mergeable Clauses
Reference #: 260127.1157.24336
Some users found that mergeable clauses no longer appeared in documents with the correct formatting. In many cases, documents generated with inserted clauses showed unexpected extra line breaks—both within the clause content and immediately before the clause itself. This caused sentences to be split apart and altered the overall layout of the document.
When merging a clause into a document, the system introduced additional paragraph breaks that were not part of the original clause. These formatting issues affected a variety of scenarios, including:
- Clauses placed back‑to‑back or inline with other content
- Clauses that appear in multiple locations within the same document
- Clauses with numbering or cross‑references
- Inline text replacements
- Formatting applied according to clause configuration
- Situations where empty paragraphs should have been removed after a placeholder was replaced
As a result, merged documents did not reflect the intended structure or appearance defined in the template or clause settings.
We resolved the issue so that clause content is inserted exactly as configured—without adding unintended line breaks or altering spacing.
RESOLUTION: Document Conversion Errors When Sending Files for IntelliSign
Reference #: 260127.1157.23797
Users encountered an error when sending documents for signature through IntelliSign using a specific document template. The issue did not occur when the document was converted to PDF manually, leading users to believe the problem was related to text boxes or formatting within the Word version of the file.
The affected template included complex text layout elements in both the document header and the body. This formatting prevented the system from successfully converting the Word file to PDF during the IntelliSign/IntelliSignNow process.
The issue has been resolved so the file converts to a PDF as expected so the document can be sent for signature.