Skip to main content
Mitratech Success Center
Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.

 

TAP 1.24.1 Release Notes

  1. Last updated
  2. Save as PDF

Release Notes – Version 1.24.1

Release Date: 20-02-2026

Release Summary

The TAP 1.24.1 release focuses on new features and key bug fixes. 

Enhancements

  1. Stronger Record Linking. Smarter Workflows. Greater Flexibility.

    The latest enhancement introduces powerful new capabilities for mapping parent–child relationships directly within workflow configurations. Administrators can now create, update, and dynamically link custom object records with greater precision — whether the parent record is created through a Support push or selected using a TeamConnect Record Search.

    Enhanced Parent–Child Record Mapping

    Record relationship configuration has been streamlined to support more advanced and scalable workflows. Administrators can now:

  • Create and link parent and child records in a single form submission
  • Reference Support pushes across stages and relationships
  • Map parent records using Support push outputs or Record Search fields
  • Maintain or override parent relationships during record updates
  • Configure one-to-many relationships without restarting workflows

For detailed information, refer to the Map Parent–Child Custom Object Relationships in Workflows page.

  1. Smarter Forms. Dynamic Filtering. More Accurate Data Entry.

    This release introduces Dependent (Cascading) Dropdown Lists directly sourced from TeamConnect lookup tables, allowing administrators to configure dropdown fields that dynamically filter options based on prior selections. Values are sourced in real time from TeamConnect lists, including multi-level hierarchies, ensuring users see only relevant choices while maintaining alignment with the TeamConnect object structure and improving data accuracy.

    Enhanced Dependent (Cascading) Dropdown Configuration

    Form configuration now supports more intelligent and flexible dropdown behavior. Administrators can now:

  • Configure cascading dropdowns using TeamConnect list fields
  • Support multi-level hierarchies or skip intermediate levels
  • Display one hierarchy level per dropdown or the full hierarchy in a single dropdown
  • Map selected values directly to TeamConnect records using TeamConnect Support
  • Build multi-step parent → child → grandchild dropdown sequences with built-in validation

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

Issue:
Previously, workflows using an Auto Submit relationship to create a TeamConnect record became stuck in the first stage, causing a submission error and preventing the record from moving to the second stage.

This issue has been resolved. The TeamConnect record is now created in the second stage, and the workflow proceeds as expected.

Case Number: 2025-1217-8872087
Impacted Areas
Auto-Submit 

Issue:
Previously, TAP dropdown fields did not always align with the intended TeamConnect field mapping in certain environments. As a result, a broader set of lookup values was displayed instead of the mapped custom values.

 

This issue has now been resolved. TAP consistently honors the configured field source and displays values only from the appropriate lookup table.

Case Number: 2026-0203-8919045

Impacted Areas
Dropdown field mappings and lookup tables.

Issue:
Previously, the Country of Matter and Country of Paying Unit fields did not display their selected values in the TAP Audit Trail, appearing blank despite being correctly mapped from TeamConnect. Other mapped fields displayed as expected, and editing the request in later stages showed only the underlying tree position.

This issue has now been resolved. All mapped fields, including Country of Matter and Country of Paying Unit, now correctly display their selected values in the TAP Audit Trail and when using Edit Request.

Case Number: 2026-0126-8908936

Impacted Areas
Audit Trail for mapped dropdown fields

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

Issue:
Previously, workflows initiated via API did not correctly map newly added TeamConnect lookup values to the TAP record. While existing values worked as expected, new values did not appear in the Audit Trail, and the Show_previousResult_ field displayed incorrect data.

This issue has now been resolved, and newly added lookup values are correctly mapped and displayed in the TAP record and Audit Trail.

Impacted Areas
TeamConnect lookup values

Known Issues

  1. 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. 
  2. 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. 
  3. 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.
  4. When the UpdateWorkflowFields API is executed, only new fields are updated, while fields that already contain data remain unchanged. 
  5. Workflows may be stuck and fail to display the Edit Request or Cancel Request actions when a relationship is named “Cancelled.” 
  6. 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.”
  7. TeamConnect Record Search currently supports only Text, Number, and Memo Text fields as search criteria. Selecting other field types (such as Parent Project or list-based fields) will result in an “invalid search clause” error from the TeamConnect API.

The following field types are not supported:

  1. Date
  2. Checkbox
  3. List / Multi-Value List
  4. Label Only
  5. Involved
  6. Custom Object
  7. Parent Project