TAP 1.23.5 Release Notes

Release Summary

The TAP 1.23.5 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, when ‘Auto-Submit’ was enabled in a relationship, fields marked with ‘Submit Even If Hidden’ were unintentionally submitted even if their values were not saved. Now, the system ensures that hidden or unsaved field values are not submitted when Auto-Submit is used.
Case Number: 2023-0615-7880611
Impacted Areas
Workflow Submit

---

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

---

Internal Fixes

Issue: Previously, when Auto-Submit was configured without a delay, File Upload and Checkbox values from the previous stage were unintentionally carried over to the next stage, while other field types (text box, multiselect, dropdown) behaved correctly. Now, the workflow ensures that no unsaved or unchanged field values are forwarded, and the Edit Request Summary for Stage 2 correctly displays “No fields were changed.”
Impacted Areas
Auto Submit 

---

Issue: Previously, when users saved form field values and applied a Hidden condition, those values were still carried forward to the next stage if Auto-Submit without delay was enabled. Now, hidden field values are correctly excluded, ensuring that data marked as hidden does not carry over to subsequent stages.
Impacted Areas
Auto Submit stage 

---

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 Auto-Submit Without Delay was used with hidden fields, the Audit Trail summary displayed incorrect Stage 1 information and did not show previously saved values. Now, the Audit Trail correctly displays Stage 1 updates with all previously saved values, ensuring accurate and consistent audit information.
Impacted Areas
Audit Trail 

---

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: Previously, when Submit Even If Element Hidden was enabled along with Auto-Submit Without Delay, form field values were not saved. As a result, the values did not appear in the Edit Request view or the Audit Trail. Now, hidden form field values are correctly saved and consistently reflected in both the Edit Request screen and the Audit Trail.
Impacted Areas
Auto Submit 

---

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.