TAP 1.23.6 Release Notes

Release Summary

The TAP 1.23.6 release focuses on enhanced security and performance, including upgrades for improved logging, bulk data upload operations, and key bug fixes. 

Enhancements

ARIES Chat Interface Updates

We’ve made minor improvements to the ARIES chat interface to enhance usability and provide a smoother user experience.

Application Upgrades

We updated the database project configurations to align with the latest supported .NET Framework and SQL Server compatibility levels. This ensures consistency across build modes, improves performance and security, and enhances long-term compatibility with our current production environment as part of our ongoing modernization efforts.

Bug Fixes 

Issue: Previously, e-Signature expiration settings did not trigger as expected, and records failed to expire. Now, expiration settings work correctly, and records expire based on the configured timeframe.
Case Number: 2025-0708-8664417
Impacted Areas
e-Signature Functionality

Issue: Previously, header logos configured in TAP → Document Builder → Header & Footer were not consistently rendered in DocuSign. Image-only headers were dropped, and in some cases, even images with adjacent text failed to appear. Now, the rendering logic has been corrected so that header images always display in the final DocuSign document, regardless of whether they appear alone or alongside text. For more information, refer to the Document Builder page.
Case Number: 2025-0808-8704991
Impacted Areas
Headers and Footers in Document Builder

Issue: Previously, banners added through the Header & Footer section in Document Builder did not appear in the generated PDF, even though the same banner displayed correctly when manually inserted in the document body. Now, the issue has been resolved so that banners added in the Header & Footer section render consistently across all pages of the generated PDF, eliminating the need for manual placement.
Case Number: 2025-0516-8603028
Impacted Areas
Headers and Footers in Document Builder

Issue: Previously, workflow formulas were not running during the auto-submit stage, causing calculated fields like Name and Year to appear blank in the Audit Trail and Dashboard. Although the API call and auto-submit completed successfully, the formulas did not execute. Now, the formulas run as expected, and the fields populate correctly.
Case Number: 2025-1203-8857026
Impacted Areas
Auto-Submit stage

Internal Fixes

Issue: Previously, users encountered a submission error when attempting to submit an e-Signature form without configuring document expiration in the Expiration tab. Now, workflows submit successfully even when no expiration settings are defined.
Impacted Areas
e-Signature support

Issue: Previously, when ‘Submit Even If Element Hidden’ was enabled, hidden field data did not appear in the Audit Trail. For example, in Stage 1, the Formula Loading Completed field did not display its expected value of True. Now, hidden field values are correctly recorded and displayed in the Audit Trail, ensuring that fields like Formula Loading Completed show their proper values.
Impacted Areas
Audit Trail 

Issue: Earlier, PDF and DOCX files were generated without their headers and footers. This issue has now been fixed, and the documents correctly include both the header and footer as expected.
Impacted Areas
Headers and Footers in Document Builder

Known Issues

1. Banner images added in the Document Builder header and footer sections are not displayed in the generated document. This occurs because these templates have fixed margins with limited header and footer space (approximately 30–37 pixels in height). Images exceeding this height are not displayed.
   Workaround: Users are advised to use or resize images to fit within the specified height constraint. 
2. When generating an e-signature document in PDF format, the header banner image may overlap with other text elements in the document. This behavior occurs due to layout and spacing constraints specific to PDF rendering. 
3. When banner images fail to load in the document header or footer, the alternate text should appear, but currently neither the image nor the alternate text is displayed. 
4. Banner images inserted with adjacent text in the Document Builder header or footer do not appear in PDF outputs. The inserted images are not rendering in the header/footer of the generated PDF. 
5. The "On Submit" Form Mapping condition with the "Area Filled" rule does not work when "Submit Even If Element is Hidden" is unchecked.