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

  1. Last updated
  2. Save as PDF

Bug Fixes

Issue: Bulk user update is done and API is not updating the use status from inactive to active. 
Tracking Code: TAPSUP-7105
Case Number: 2023-0711-7907472
Reported Version: 1.14.3.0
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

  1. Open the Postman portal/app.
  2. Use the "bulkAddOrUpdate" API with the necessary details.
  3. Click the API and get the response.
     

Expected Results of Steps
A large number of users should be made active/inactive through the API.

Actual Results of Steps
A large number of users can be locked, but cannot be unlocked through the API.

Root Cause Analysis
The code is using "false" as the default value for the "isLocked" variable.

Impacted Areas

  1. Lock and Unlock the User through API
  2. Lock and Unlock the User from TAP UI.

Tested Areas

  1. Lock and Unlock the User through API
  2. Lock and Unlock the User from TAP UI.

Issue: Certain text boxes are unusable /un-editable when previewing workflow
Tracking Code: TAPSUP-7258
Case Number: 2023-0718-7915483
Reported Version: 1.14.3.0
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

  1. Import or create a workflow.
  2. Add cells to the document builder.
  3. Save and preview the workflow.

Expected Results of Steps
The cells should be in the sections specified by the client and must be editable.

Actual Results of Steps
The cells either disappear or move to the corner of the column, causing it to split into two cells.

Root Cause Analysis
There is an issue with using editable spaces under table columns. It works fine outside of tables in the CKEditor 5 document field.
To fix this, we need to either:

  • Add a placeholder inside the editable text box.
  • Implement a code fix to retain spaces when loading or previewing the workflow.

For now, we have to remove the content and add editable spaces again where needed.

Impacted Areas
Document builder

Tested Areas

  1. Ckeditor5 document field with editable spaces and without editable spaces (restricted mode on)
  2. Ckeditor5 document field with editable spaces and without editable spaces (restricted mode off)

Issue: Drop-Down picking up a different language
Tracking Code: TAPSUP-8104
Case Number: 2024-0116-8113309
Reported Version: TAP 1.15.7.0
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

  1. Go to the workflow.
  2. Fill in the intake form and choose the country.
  3. Submit the form.

Expected Results of Steps
The selected country should be displayed in the View history.

Actual Results of Steps
The Country field is displayed in the language of the selected country.

Root Cause Analysis
For the grid data source, the behavior is to pick values from value_text  in the request. For all other data sources, values are taken from value in the request.
When using Google Translator, value_text gets translated to a different language and this translated value is saved in the database. As a result, the Audit trail displays the translated value_text.
To fix this issue, we need to pass the direct value to resultData.ValueText just like we do for other data sources.

Impacted Areas
Audit Trail page

Tested Areas

  1. External API from stage and relationship with grid data source dropdown fields (used Google Translator before selecting the option)
  2. Workflow formula verification with grid data source dropdown fields (used Google Translator before selecting the option)
  3. Form mapping with grid data source dropdown fields (used Google Translator before selecting the option)
  4. Form submission with translated and non-translated values (verified results on the Audit Trail page)

Issue: "Search Requests" feature on the dashboard is not filtering the requested values.
Tracking Code: TAPSUP-8136
Case Number: 2024-0201-8131723
Reported Version: TAP 1.15.9.1
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

  1. Go to “Pinned Filter Setup” → Create a workflow dashboard filter with advanced pop-up configuration.
  2. Go to the workflow dashboard and click on the filter created in the previous step.
  3. In the "Advanced Search" pop-up, try searching in the "Contract Party Name" field. It will not filter the exact values and will display all records.

Note: The issue occurs only when the client dashboard stored procedure is enabled; it does not occur if the stored procedure is disabled. Also, the Grid Configuration file was added.

Expected Results of Steps
The "Search Request" feature on the dashboard should display the values entered in the fields.

Actual Results of Steps
The "Search Request" feature on the dashboard is not working correctly, as it fails to filter the requested values and displays all records.

Root Cause Analysis
There is an issue with the C# code where advanced filters are not being attached to the WHERE clause.

Impacted Areas
Advanced Search Feature

Tested Areas

  1. Advanced search with the filter.
  2. Export with an advanced search.
  3. Submit any workflow with Japanese text in a dynamic column.
  4. On the dashboard, column filters were applied and verified.
  5. On the dashboard, global search were applied and verified.
  6. On the dashboard, advanced filters were applied and verified.

Issue: Child workflow feature not working while mapping workflow name.
Tracking Code: TAPSUP-8276
Case Number: 2024-0311-8174573
Reported Version: TAP 1.16.3
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

  1. Create Child and Parent Workflows.
  2. Add mapping on the first stage of the Child Workflow and enable "Use Workflow Name" in mapping.
  3. Submit the Parent Workflow.

Expected Results of Steps
The request for the child workflow should be seen being created on the Dashboard.

Actual Results of Steps
The request for the child workflow is not seen as being created on the dashboard.

Root Cause Analysis
The Null exception was not handled properly. ResultSet needs to be initialized before use.

Impacted Areas
Child Workflow

Tested Areas

  1. Child Workflow
  2. Form mapping in child and parent workflows (On Submit only)
  3. API Initiate and Continue for child workflow setup
  4. Autosubmit process with child workflow setup
  5. Save Workflow functionality

Issue: Certain editable text boxes are missing in the document field when we preview the workflow. This specific form can be found when options “Film” and Loanout = “No” in the workflow attached. 
Tracking Code: TAPSUP-8459
Case Number: 2024-0516-8245741
Reported Version: TAP 1.16.3
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

  1. Preview the attached workflow.
  2. Enter the options 'Film' and 'No'.
  3. Submit the workflow to the next stage.
  4. Some editable text boxes will be missing.

Expected Results of Steps
Editable text boxes should not be missing.

Actual Results of Steps
Certain editable text boxes may not appear.

Root Cause Analysis
There's an issue when using editable spaces under table columns, but it works fine outside of tables in the CKEditor5 document field. To fix this, we can either add a placeholder inside the editable text box or apply a code fix to preserve the spaces when loading or previewing the workflow.

Impacted Areas
Editable spaces under table columns

Tested Areas
The following scenarios using designer load after workflow save and preview of the saved workflow:

  1. CKEditor5 document field with editable spaces and without editable spaces (with restricted mode on).
  2. CKEditor5 document field with editable spaces and without editable spaces (with restricted mode off).

Note: The editable spaces are placed under table columns for each test.

Issue: Records of Japanese characters are not getting displayed on the dashboard when we filter using Japanese characters even though there are records with that criteria on the workflow.
Tracking Code: TAPSUP-7370
Case Number: 2023-0907-7976149
Reported Version: 1.14.3.0
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

  1. Go to the Dashboard and select the Japanese filter options.
  2. In any column, add Japanese characters to filter records.
  3. The filter doesn't recognize Japanese characters and doesn't show matching records, even though such records exist in the workflow. 

Expected Results of Steps
Records with Japanese characters should be displayed on the dashboard when filtered using Japanese characters in the corresponding column field.

Actual Results of Steps
Records with Japanese characters are not displayed on the dashboard when filtered using Japanese characters, even though matching records exist.

Root Cause Analysis
Issue with C# and SQL query: Japanese characters are converting into unidentified characters ("???????") when passed as parameters to the stored procedure.

Impacted Areas

  1. Dashboard filter for dynamic columns
  2. Dynamic columns search

Tested Areas

  1. Dashboard filter for dynamic columns
  2. Dynamic columns search

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Topic
  2. Tags
    1. 1.17.6
    2. 1.17.7
    3. 1.17.7 Release Notes
    4. TAP 1.17.6
    5. TAP 1.17.6 Release Notes