TAP 1.23.2 Release Notes

Release Summary

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

Enhancements

Document Attachment/Removal Notification

We have added a new notification feature in TAP’s Collaboration Stage to alert users when documents are attached or removed without a comment. Administrators and users can now enable separate notifications for document addition and removal, keeping all participants updated on important changes in real time. These enhancements help users stay informed about document changes in TAP, reducing missed updates and the need for external communication.

Key improvements:

• New checkboxes under Collaboration Stage → Default Subscriptions to control document attachment/removal notifications.

• Dedicated notification templates for both actions, with rich text editing and dynamic tokens.

• Notifications are sent only when a document is attached or removed without a comment, and the subscription is enabled.

• All Collaboration Stage participants receive these notifications, with flexible admin and user-level settings.

For more information, refer to the Collaboration Stage page.

Standardized TeamConnect References

• All references to TeamConnect across TAP have been standardized to use the correct compound word format with capital T and C (TeamConnect), replacing incorrect variations such as teamconnect, Teamconnect, or Team Connect.
• The Multi Select form field now references “Multi-Value list” instead of “Multi Item Lookup Table.”
• Selection prompts and tooltips have been updated for consistent terminology (“Multi Value List”).
• Error messages have been revised to display “Unable to Retrieve Data, Review Your TeamConnect Key” when data cannot be retrieved.
• A new warning message appears during workflow import with an invalid TeamConnect Key: “All TeamConnect Support configurations will be deleted as the TeamConnect Key does not contain the following Object Types.”

Category Dropdown Fix in TeamConnect Support

The TeamConnect Support page has been enhanced so that when updating an existing object, the “Select primary category” dropdown now correctly displays the name of the root category for the selected object, instead of showing a blank space. This improves clarity and usability for users managing object categories.

                               Before                                                                                                                      After

Application Upgrades

We’ve upgraded the application’s underlying frameworks, including .NET and Entity Framework, to strengthen our security posture, improve system performance, and align with modern development standards. These upgrades also ensure long-term supportability, compatibility with evolving infrastructure, and future integrations. This is part of an ongoing modernization initiative.

Enhanced UI After Database Update

1. Previously, the system used nvarchar(max), allowing users to configure an unlimited number of form fields. To improve performance and stability, this has been updated to limit the number of form fields to a maximum of 120 when creating a group role in the Workflow tab. Users can now add up to 120 form fields. If this limit is exceeded, a UI message will appear indicating that the maximum number of fields has been reached. (TAP-57811)

2. Previously, users could configure an unlimited number of roles for AuditTrail Access and Attachments Access across form fields. To improve usability and system performance, the number of roles that can be configured has been limited to a maximum of 25. If a user attempts to add more than 25 roles, a UI error message is displayed. (TAP-57954)

Bug Fixes 

Issue: The GET Audit Trail API endpoint currently requires a request body, which is not compliant with REST standards, as it does not support bodies in GET requests. To resolve this, a new POST endpoint will be introduced to accept the required parameters in the body, while the existing GET endpoint will be deprecated for backward compatibility.
Case Number: 2025-0819-8720591
Impacted Areas
Audit Trail API endpoint

Internal Fixes

Issue: Previously, adding form fields to the subject line for Document Attached or Removal notifications did not work. The selected field was not added when clicking "Add." Now, the subject line updates correctly when a form field is added.
Impacted Areas
Document Attached or Removal Notifications 

Issue: Previously, when the “Validate date” option was enabled and a formula was applied to a DatePicker field, the system accepted dates with a format mismatch during API submission. Now, the DatePicker correctly enforces date format validation, and invalid date formats are rejected as expected.
Impacted Areas
Date Picker Field 

Issue: Previously, saving privileges in Application Permissions would sometimes display a “Failed to save role privileges” error message, and the changes were not saved. Now, privileges are saved correctly without error.
Impacted Areas
Application Permissions Privileges

Issue: Previously, the DatePicker field incorrectly displayed an error during submission, even when valid data was entered. Now, the DatePicker functions as expected, no error is displayed, and the form submits successfully
Impacted Areas
Date Picker Field

Known Issue(s)

1. When saving an "Update Salesforce Object" configuration without selecting any Salesforce object, the system throws an exception requiring at least one object to be selected, even if no mandatory fields are present.