TAP 1.24.4 Release Notes

Release Summary

This release delivers key security and performance enhancements, along with improvements to e-Signature usability and database efficiency. It also introduces API upload support, better search configuration guidance, and an updated feature request experience, key bug fixes, and known issues. 

Security Improvements 
This release includes multiple security enhancements and fixes to strengthen the platform and address issues identified during internal security reviews. 

e-Signature Improvements 
This release removes password protection from documents downloaded via the e-Signature preview, allowing users to view and edit documents without restrictions.

Note: This change is not enabled by default and can be made available to any customer upon request, based on their specific requirements. 

Database and Performance Improvements
This release includes enhancements to improve database performance, scalability, and maintainability. As part of ongoing platform optimization, data management has been optimized, and key queries have been refined to reduce delays and improve overall application responsiveness. 

Enhancements

External API – Multipart/Form-Data Support 
The External API module now supports multipart/form-data as a content type for document upload requests. This enhancement enables integrations with third-party APIs that require file uploads or form submissions containing both text and binary content in a single request. Existing integrations that use previously supported content types continue to function without any changes.
For more information, see the External API – File Upload Support page.

TeamConnect Record Search Enhancements
This release improves usability in the TeamConnect Record Search Configuration by introducing tooltips that clearly indicate supported and unsupported field types. Unsupported fields are no longer grayed out; instead, users receive visual cues and messages when selecting unsupported types, while valid selections display contextual guidance. Existing workflows remain unaffected, and validation is enforced only for new configurations. For more details, refer to the TeamConnect Record Search page.

Feature Requests Redirect Update
The Feature Requests option under the Help menu has been updated to redirect users to Productboard instead of the previous Aha Ideas portal, providing a more streamlined experience for submitting and tracking product feedback. 

---

Bug Fixes 

Issue:
Previously, documents downloaded from the eSignature preview in TAP were being saved as password-protected files, preventing users from editing them.
This issue has been resolved so that downloaded documents are no longer password-protected and can be edited as expected.
Case Number: 2025-0130-8496094
Impacted Areas
eSignature Preview / Document Download (DocuSign and Adobe Sign)

---

Issue:
Previously, some users encountered errors when submitting requests using DocuSign integration, even though their accounts were correctly configured in both DocuSign and TAP.
This issue has been resolved so that users can submit requests successfully without encountering eSignature errors.
Case Number: 2024-1008-8397992
Impacted Areas
DocuSign Integration 

---

Issue:
Previously, users encountered an error when submitting a request to the Credit Team stage, preventing the workflow from progressing.
This issue has been resolved so that requests can now be submitted to the Credit Team stage without errors.
Case Number: 2025-0303-8524645
Impacted Areas
Stage Submission

---

Issue:
Previously, updating user roles and departments through CSV import triggered a password reset for the affected users, requiring them to set a new password on their next login.
This issue has been resolved so that updating user details via CSV import no longer resets user passwords.
Case Number: 2025-0416-8571878
Impacted Areas
CSV Import

---

Issue:
Previously, table fields were inconsistently available across features, where they appeared in Document Builder but were not selectable in the Notification “Form result value” configuration.
This inconsistency has been resolved to ensure table fields are handled consistently across features.
Case Number: 2025-0611-8631752
Impacted Areas
Document Builder / Form Fields

---

Issue:
Previously, values with trailing spaces in grid data source CSV files were not displayed correctly when used in Conditions, causing saved values to appear blank during editing.
This issue has been resolved so that values are displayed correctly even if the source data contains trailing spaces.
Case Number: 2025-0626-8650193
Impacted Areas
Conditions

---

Issue:
Previously, the Categories field did not display any values when editing certain requests, even though it was correctly configured to retrieve data.
This issue has been resolved so that the Categories field now displays the expected values when editing the request.
Case Number: 2025-0716-8673301
Impacted Areas
Categories Field

---

Issue:
Previously, users encountered an “Email could not be sent” error during request submission for certain records, preventing the workflow from completing successfully.
This issue has been resolved so that requests are submitted successfully, and notification emails are sent as expected.
Case Number: 2025-0916-8761475
Impacted Areas
Request Submission

---

Issue:
Previously, the Spreadsheet form field did not function in anonymous access scenarios and appeared blank to users.
This issue has been resolved so that the spreadsheet field now works correctly and displays data when accessed anonymously.
Case Number: 2025-0930-8780205
Impacted Areas
Spreadsheet Field

---

Issue:
Previously, files stored in the Content Library could be indexed by search engines and appear in public search results, making them discoverable externally.
This issue has been addressed by preventing search engine indexing, so Content Library files no longer appear in search results while remaining accessible via direct links as intended.
Case Number: 2026-0304-8952943
Impacted Areas
Content Library

---

Issue:
Previously, table fields were not available for selection in the Form Result Value option across various notification and document configuration screens.
This issue has been resolved so that table fields are now available for selection where applicable.
Impacted Areas
Document Builder 

---

Issue:
Previously, table fields in eSignature expiration notification subject lines displayed internal data instead of the field caption.
This issue has been resolved, and the subject line now displays the correct table field caption as expected.
Impacted Areas
eSignature Notifications 

---

Issue:
Previously, extra spaces in values caused conditions to be evaluated incorrectly, preventing the Submit button from being displayed even when the condition was met.
This issue has been resolved so that conditions are evaluated correctly, and the Submit button is displayed as expected.
Impacted Areas
Submit Button

---

Issue:
Previously, users encountered an internal error when saving workflows that included TeamConnect (TC) fields, preventing the workflow from being saved and accessed.
This issue has been resolved so that workflows with TC fields can now be saved and edited without errors.
Impacted Areas
Workflow Configuration

---

Issue:
Previously, the Spreadsheet form field displayed as blank when configured with a 1/2 alignment.
This issue has been resolved, and the spreadsheet field now displays correctly regardless of alignment settings.
Impacted Areas
Spreadsheet Field 

---

Issue:
Previously, request numbers were inconsistently displayed between the dashboard and audit trail, leading to mismatched and skipped sequence values.
This issue has been resolved so that request numbers are now generated and displayed consistently across the dashboard, audit logs, and view history.
Impacted Areas
Audit Trail 

---

Issue:
Previously, the Cell Name field retained user input from Spreadsheet configurations, causing unintended cell references to appear in the notification body when adding Table fields.
This issue has been resolved by ensuring the cell reference is cleared or ignored when switching to a Table field, preventing unintended content from being included.
Impacted Areas
Notification Editor

---

Known Issues

1. When accessing workflows anonymously, the Spreadsheet form field may not function as expected and can appear unusable, even though it worked in earlier versions.
2. When multiple Spreadsheet fields are included, the layout in the exported PDF may not render as expected, which can affect the display of spreadsheet data. 
3. When the row size increases in a Spreadsheet field, the spreadsheet data in the exported PDF may not remain aligned in its expected position. 
4. When exporting data in bulk, Spreadsheet field data may be misaligned if some cells are left empty, causing values to shift from their expected positions. 
5. In DocuSign eSignature notifications, the document name may not display as per the configured custom name. 
6. When “Submit without template” is enabled in eSignature setup, the document name may not display as per the configured custom name in eSignature notifications.