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.21 Release Notes

  1. Last updated
  2. Save as PDF

Production Date: 05-02-2025

Release Summary

The TAP 1.21 release includes technical maintenance such as library upgrades, bug fixes, internal defects, and known issues for a better user experience.

Technical Maintenance 

  • jQuery UI Upgrade
  • Security enhancements
  • TAP Teams Upgrade

Upgrade(s) Edit section

jQuery UI Upgrade: To strengthen the security of our web application, we've upgraded JavaScript libraries to the latest versions. This ensures enhanced protection against potential threats and provides a more secure and reliable experience for our users.

Affected Areas Due to jQuery UI Upgrade:

  • Grids:
    • Dashboard, Document Repository, Document Library grids (sorting, filtering, pagination, configuration popups).
  • Pages:
    • Dashboard, Document Repository, Document Library grids and popups.
  • Designer Page:
    • Element drag and drop - When dragging an element into the section, its length is larger than the placeholder.
    • Field properties and styles of elements.
  • Popups:
    • Conditions, notifications, form mapping, roles, embed, and workflow templates options.
  • Workflow Role Popup:
    • Alignment of elements corrected.

TAP Teams Upgrade: To enhance functionality and improve user experience, we've upgraded to the latest version of TAP Teams. 

Update Required: CSP Configuration for SSO Access via Microsoft Teams
To support seamless Single Sign-On (SSO) for TAP users accessing Microsoft Teams (desktop or browser), an update to your Content Security Policy (CSP) configuration is required. This update allows authentication and resource loading from external identity providers (IDPs). It applies to all IDPs—including but not limited to Okta—used for SSO integration with TAP. Users may experience login issues or problems loading components within the Teams app without this update.
This update is necessary as Microsoft is consolidating user-facing Microsoft 365 apps and services under a single domain: cloud.microsoft. For more details, refer to the Microsoft documentation: https://learn.microsoft.com/en-us/microsoft-365/enterprise/cloud-microsoft-domain?view=o365-worldwide

Action Required:
Update the Content-Security-Policy in your IDP configuration to include the following under the frame-ancestors directive: https://*.cloud.microsoft  
This change ensures the IDP login page can be embedded within the new Microsoft Teams experience (e.g., https://teams.cloud.microsoft).

Bug Fixes 

Issue: Submitting all stages was resulting in an error, even though all stages were expected to submit without issues.
Case Numbers: 2025-0313-8536088
Impacted Areas
Stage Submit
Expected Behavior:
While the UI allows up to 1016 input characters, the system adds extra characters—specifically a comma and space (, )—between each parallel relationship when saving data to the workflowstatus column.
For example, if a user adds five parallel relationships, the system adds 8 extra characters. As a result, the total character count in the column depends on the number of parallel or conditional relationships, and these added characters count toward the 1024-character limit.

Internal Fixes

Issue: Dynamic columns are not displaying on the Analytics and Datasets pages, preventing users from viewing expected data insights.
Impacted Areas
Datasets pages

Issue: The "Dropdown Group Type" option is incorrectly appearing when the Role Type is set to "Group of Users," even though a new Group Type dropdown is not available.
Impacted Areas
Roles

Issue: The configuration is getting saved even when an error message for invalid input is displayed instead of preventing the save action as expected.
Impacted Areas
External API Trigger

Issue: The "Email" column name is being truncated in the Workflow Roles section. Even though the name is lengthy, it should be displayed in full.
Impacted Areas
Email Column Name

Issue: Changes made to User Generic Fields are not being saved as expected.
Impacted Areas
User Generic Fields

Issue: Users are unable to save the External API configuration or the workflow when using the TAP Create Token API, as it results in a submission error.
Impacted Areas
TAP API Trigger

Issue: The UI on the Thank You page displays unexpected extra content when the external API call fails.
Impacted Areas
Thank you page

Issue:  The "Additional Condition" popup is showing up from the form element in the stage conditions, causing the form element condition to appear in the stage condition popup.
Impacted Areas
Stage Condition

Issue: An extra scrollbar was appearing in the Relationship Conditions popup when more than 8 conditions were added. This has been fixed to ensure only one scrollbar is displayed.
Impacted Areas
Relationship Conditions pop-up

Known Issues

  1. When previewing a form configured with a Form Wizard, if a user opens a dropdown located at the bottom of a section, they may experience difficulty navigating to the next section. The section does not switch on the first click — the user needs to click twice for the navigation to occur.
  2. When previewing the workflow, there is missing spacing between the label and its corresponding field.
  3. Spreadsheet custom formula validation is not working correctly in workflows.
  4. The Email dropdown supports up to 100 characters. If the value exceeds this limit, the dropdown UI is misaligned.
  5. Existing user records are being updated during import even when the "Update Existing Users" option is not selected, and duplicate entries are not being ignored.
  6. In the "Initiate Workflow by Email" feature, validation error notifications for missing attachments are still being sent to the requester even when the "Send Validation Error to Requester" option is unchecked.
  7. In the custom HTML field with a popup, enabling the "Show by Default" checkbox causes the popup to open on preview as expected. However, the popup header is getting overlapped by the top border of the Microsoft Teams iframe.
  8. In the TAP application, when accessing the Signature Repository and initiating the Clone action, the redirection to the Signature page after clicking the Send button does not load the page correctly.
  9. The tooltip for the MS Teams iframe workflow title does not handle extra spaces correctly. While TAP normalizes multiple spaces into a single space in the workflow title, the tooltip in MS Teams retains the original spacing, causing a mismatch between the displayed title and the tooltip content.
  10.  Document form field data is not appearing in the received e-signature document.
  11. An opaque background block appears behind the translucent dragged field when dragging a form field into the form area and holding it in place. This background block is slightly larger than the form field being dragged.




 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Topic
  2. Tags
    1. 1.21 release Notes
    2. JQuery Upgrade
    3. TAP 1.21 Release Notes