TAP 1.24 Release Notes
Release Notes – Version 1.24
Release Date: 06-02-2026
Release Summary
The TAP 1.24 release focuses on new features and key bug fixes.
Enhancements
- Admins can now link TeamConnect object records in a parent–child relationship seamlessly across workflow stages using TeamConnect Support and record search. For detailed information, refer to the Map Parent–Child Custom Object Relationships in Workflows page.
- Admins can now configure dependent (cascading) drop-downs using TeamConnect lists, enabling dropdown options to filter dynamically based on prior dropdown selections, and more accurate data entry in forms. For detailed information, refer to the Configure Dependent (Cascading) Dropdown Lists page.
Bug Fixes
Issue:
Previously, some workflow requests that followed a relationship named “Cancelled” appeared to be auto-cancelled immediately after a review stage, even when users attempted to resubmit or create duplicate requests.
The workflow engine has now been updated so that the “Cancelled” relationship name is no longer treated as a special keyword. Requests that follow a relationship named “Cancelled” now follow the configured workflow logic without being incorrectly marked as system-cancelled, allowing workflows to progress through the relevant review stage as expected.
Case Number: 2025-0407-8559924
Impacted Areas
Relationships named ‘Cancelled.’
Issue:
Previously, newly added values in a TeamConnect lookup list did not automatically sync with TAP dropdown fields. As a result, selecting a new first item caused formula fields to miss the value, requiring users to manually open field properties and save the workflow to refresh the dropdown.
This issue is now resolved. TAP dropdowns automatically sync with TeamConnect lookup lists, and formula fields correctly capture newly added values on first selection, ensuring workflows run smoothly without manual intervention.
Case Number: 2025-0910-8753840
Impacted Areas
Drop-down fields and Formula fields
Issue:
Previously, when a TAP text field populated by a formula or manual entry contained square brackets ([ or ]) and was submitted to a custom text field in TeamConnect, the record failed to submit. Users saw a generic error message: "There was an error on the Page. Please contact the Administrator." As a result, the record was not created in TeamConnect.
This issue has now been resolved. TAP records containing square brackets in text fields can be successfully submitted to TeamConnect custom text fields, ensuring that all data is correctly passed and stored.
Case Number: 2025-0918-8765364
Impacted Areas
Text fields
Issue:
Previously, when changes were made to the External API (API URL) configuration, saving the updates resulted in an error, and the changes were not successfully saved.
This issue has now been resolved. Updates to the External API (API URL) can now be saved successfully without triggering an error message, ensuring configuration changes are applied as expected.
Case Number: 2025-1030-8822819, 2025-1016-8803459
Impacted Areas
External API Configuration
Issue:
Previously, the TAB navigation worked only for Text, Multi-upload, Multi-select, and Dropdown fields, while other field types were skipped. This behavior occurred only after the first stage was submitted.
This issue has now been resolved. The TAB key now correctly navigates through all field types, even after the first stage is submitted.
Case Number: 2024-1014-8403244
Impacted Areas
Stage submit
Issue:
Previously, when users attempted to create a request from Salesforce using the Activate Request button, the request failed with a 500 error on the Salesforce side, and the request was not created in TAP.
This issue has now been resolved. The requests initiated from Salesforce using the Activate Request button are now processed successfully and created in TAP without errors.
Case Number: 2025-0106-8473100
Impacted Areas
Create request
Internal Bug Fixes
Issue:
Previously, workflows using a relationship named “Cancelled” became stuck and did not display the Edit Request or Cancel Request actions, preventing further progress.
This issue has now been resolved, and workflows with a “Cancelled” relationship now display the correct actions and proceed as expected.
Impacted Areas
Relationships named ‘Cancelled.’
Issue:
Previously, saving the External API configuration failed when the API URL was configured using a form field, and users received the error message “Insecure API URL (Domain/IP) entered. Please provide an alternate URL.”
This issue has now been resolved, and External API configurations using form fields can now be saved successfully without triggering an error.
Impacted Areas
External API Configuration
Known Issues
- TeamConnect Multi‑Select field values appear blank in the Audit Trail and Workflow Notifications when the list is tied to a custom lookup table that uses the same table code as an existing system lookup table. This issue does not affect TeamConnect Dropdown fields, which continue to display values correctly.
- The Record Form section may not be visible to end users even when View/Edit permissions are configured at the stage level for Record Form fields.
- An incorrect relationship status may be displayed on the dashboard when auto-submit (delay) is used with TAPSign, and the e-signature file may not be generated as expected.
- When the UpdateWorkflowFields API is executed, only new fields are updated, while fields that already contain data remain unchanged.
- Workflows may be stuck and fail to display the Edit Request or Cancel Request actions when a relationship is named “Cancelled.”
- When a workflow template that includes TeamConnect Support is imported, the workflow can be saved and previewed, but cannot be submitted. During submission, the application displays the error: “There was an error pulling the TeamConnect data. Please check your TeamConnect key.”