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

  1. Last updated
  2. Save as PDF

New Feature(s)

Adding specifics to child statement failure logs:  It has been noticed that not all client-reported failures are accompanied by child statement failure logs. Even with the existing logs, pinpointing the specific child record that encountered an issue is challenging. We included additional details such as user email, child record number, etc., to enhance the comprehensiveness of the current logs.

Impacted Areas: Child workflows.

Bug Fixes

Issue: The anonymous user is not able to initiate the workflow in the Dashboard via email.
Tracking Code: TAPSUP-7406
Case Number: N/A
Reported Version: 1.9
Workaround
None

Pre-Requisites
Access to TAP Environment.

Steps to Reproduce

  1. Create a workflow including Anonymous User.
  2. Add a text field with Email Validation.
  3. Add another text field for the email subject.
  4. Add a text area for the email body.
  5. Add a multi-file upload field.
  6. Click the Workflow tab and add 2 stages and 1 relationship.
  7. Change the form access on stage 1 to show all the fields.
  8. Under options, click ‘Anonymous access’.
  9. Check, ‘Use anonymous access’.
  10. Select the email text field and Check the ‘Use email field only’.
  11. Check ‘Initiate workflow by email’, select the email subject, and select the email body.
  12. Copy the email address under the ‘Initiate workflow by email’ option.
  13. Click Save and Publish the workflow.
  14. Send an email to the email address with a subject, body, and attachment.
  15. Navigate to the dashboard and ensure that a workflow instance was created.

Expected Results of Steps
The workflow record should be visible on the dashboard for the user.

Actual Results of Steps
The user cannot view the workflow record on the dashboard.

Root Cause Analysis
Our servers consistently query the Microsoft Authentication Library (MSAL) Token authority for an Access Token. Azure Active Directory (AAD) refers to this as throttling and imposes restrictions on clients that throttle at high frequencies. To circumvent this, manual implementation of token caching was necessary.

Impacted Areas
Emails, Workflows submitted by emails.

Tested Areas

  1. All Email communication.
  2. Workflows submitted by email.
  3. Initiate a workflow by an anonymous user.

Issue: Bug in collaboration stage with alternate language.
Tracking Code: TAPSUP-6789
Case Number: 2023-0427-7808880
Reported Version: 1.12.2.1
Workaround
None

Pre-Requisites
Access to TAP Environment.

Steps to Reproduce

  1. Go to the Designer and choose the required workflow in the collaboration stage.
  2. Preview the workflow.
  3. Attempt to submit the form in the first stage using English language.
  4. Navigate to the Dashboard, choose the request ID, and select ‘Edit request.’
  5. Upload a file to observe normal document upload behavior.
  6. Return to the workflow and repeat the steps using Portuguese.
  7. Try uploading a file in the second stage; note that the file upload is unsuccessful and generates an error.
  8. Attempt to submit the form in English and change the language in the second stage to Portuguese; observe that changing back to English does not function.
  9. Similarly, if you submit the form in Portuguese and attempt to change the language back to English in the second stage, it does not work.
  10. Note that file uploads function correctly, even in Portuguese, when the collaboration stage is not enabled.

Expected Results of Steps
The file upload in the second stage, even for the Portuguese language, should occur without encountering submission errors. 
Additionally, language changes should be possible in both directions.

Actual Results of Steps
Selecting the Portuguese language results in an error during file upload.
Additionally, changing the language back from Portuguese to English is not successful.

Root Cause Analysis
The Submit button in the collaboration stage is categorized as an element with the type ‘Button’, while in the non-collaboration stage, it is labeled as type ‘Submit’. The code was specifically designed to recognize only the ‘Submit’ type.

Impacted Areas

  1. Save, reset, print, and submit buttons with alternative language.
  2. Dropdown and Radio button with language selection in collaboration and normal stage.
  3. Collaboration section.
  4. Collaboration Member and  Editor Role.

Tested Areas

  1. Full Collaboration Stage.
  2. Form navigation buttons - save, reset, print, and submit with alternative language.
  3. Button form field with alternative language.
  4. Dropdown and Radio button with language selection in collaboration and normal stage.
  5. Full Alternative language.
  6. Collaboration section permission with and without language.
  7. Collaboration Member and Editor Role with Language.

Issue: Reminder notifications are not triggered for informational notifications.
Tracking Code: TAPSUP-7380
Case Number: 2023-0914-7984577
Reported Version: 1.15.7.0
Workaround
None

Pre-Requisites
Access to TAP Environment.

Steps to Reproduce

  1. Import the workflow.
  2. Submit the initial stage and verify its progression through the Partner Review (Training) relationship, which includes two notifications - a next action notification and an informational one.
  3. Note that the informational notification does not activate reminders, while the first notification is functioning correctly.
  4. Wait for a day to confirm if reminders are triggered.

Expected Results of Steps
Reminder notifications need to be triggered on a daily basis.

Actual Results of Steps
Reminder notifications are not triggered at all; only the initial notification is sent.

Root Cause Analysis
Initially, we attempted to decode the HTML and then create the JSON object but encountered exceptions in generating the correct JSON object. Currently, we first create the JSON object and subsequently decode the HTML.

Impacted Areas
Relationship Notifications.

Tested Areas
Relationship Notifications.

Issue: UI issue with the drop-down field.
Tracking Code: TAPSUP-7403
Case Number: 2023-0921-7993540
Reported Version: 1.15.7.0
Workaround
None

Pre-Requisites
Access to TAP Environment.

Steps to Reproduce

  1. Import the workflow.
  2. Preview the workflow and try to select options from the dropdown.

Expected Results of Steps
When attempting to choose options, the webpage position should remain unchanged.

Actual Results of Steps
The webpage undergoes a slight position change whenever we attempt to select options from the dropdown.

Root Cause Analysis
During the page load, focus is applied to all search fields of select2 controls.

Impacted Areas
Dropdown and multi-select fields.

Tested Areas
Dropdown and multi-select fields.

Issue: API Document Mapping 
Tracking Code: TAPSUP-7704
Case Number: 2023-1018-8024205
Reported Version: 1.15.7.0
Workaround
None

Pre-Requisites
Access to TAP Environment.

Steps to Reproduce

  1. Import the workflow.
  2. Pay attention to the external API configured in the 'Get File' relationship.
  3. In the 'Files' section, map the document generated from the API to the 'file from API' upload field.
  4. Submit the workflow and navigate to the dashboard to click on 'View History' for the request.

Expected Results of Steps
The API document needs to be associated with the 'file from API' field in the workflow.

Actual Results of Steps
The API document is not linked to the form field; instead, it appears under the documents section.

Root Cause Analysis
The accurate ResultData is not being inserted into the database when retrieving files from the API.

Impacted Areas

  1. Files for every relationship that has configured an API to retrieve a file.
  2. Files during both file uploads and attempts to obtain files from the API.
  3. File validation when submitting the workflow.
  4. Files when adding SplitterDocuments.
  5. API calls within child workflows.
  6. Ability to edit the request and retrieve the file.
  7. AuditTrail to observe the files obtained through API calls and view the documents by clicking on them.

Tested Areas

  1. Verify files for every relationship that has configured an API to retrieve a file.
  2. Validate files during both file uploads and attempts to obtain files from the API.
  3. Confirm file validation when submitting the workflow.
  4. Ensure proper handling of files when adding SplitterDocuments.
  5. Review API calls within child workflows.
  6. Check for the ability to edit the request and retrieve the file.
  7. Utilize AuditTrail to observe the files obtained through API calls and view the documents by clicking on them.

Issue: Signature Repository Actions 
Tracking Code: TAPSUP-7707
Case Number: 2023-1018-8024797
Reported Version: 1.15.7.0
Workaround
None

Pre-Requisites
Access to TAP Environment.

Steps to Reproduce

  1. Navigate to the Signature Repository within the Document Library. 
  2. Access the console logs, perform a hard reload of the page, and inspect all user records.

Expected Results of Steps
Users should be able to access the 'Action' feature.

Actual Results of Steps
Users are unable to access the 'Action' feature.

Root Cause Analysis
Invoked a function (isOfflineActiveWorkflowExists) that had not been loaded when invoked.

Impacted Areas

  1. Grid actions in the Document Repository.
  2. Grid actions in the the Revisions Area.
  3. Grid actions in the Signature Repository.
  4. Grid actions in the Workflow Dashboard.


Tested Areas

  1. Verified that we don’t have console errors when loading the next scenarios.
  2. Grid actions into Document Repository.
  3. Grid actions into the Revisions Area.
  4. Grid actions into Signature Repository.
  5. Grid actions into Workflow Dashboard.
  6. PWA testing.
  7. PWA online mode testing with IPAD.

Issue: Unable to view history for a few old records. 
Tracking Code: TAPSUP-7708
Case Number: 2023-1019-8026569
Reported Version: 1.15.7.0
Workaround
None

Pre-Requisites
Access to TAP Environment.

Steps to Reproduce

  1. Search for any older records created before 2017. 
  2. Navigate to Actions → View History, or Actions → Documents.

Expected Results of Steps
Upon selecting "View History," the audit trail for the record should be visible.

Actual Results of Steps
The page displays an error message: "There was an error on the page. Please contact the Administrator."

Root Cause Analysis

  1. Some older records, those created on or before 2017, cannot be opened in the view history, throwing a backend error: "Object reference not set to an instance of an object." However, the documents and edit tabs can still be accessed for these records.
  2. In the case of certain older records, users encounter difficulties accessing the documents and view history tabs, resulting in a backend error stating "invalid refresh token." These records, generated using the Echosign integrator, have expired tokens, causing this error to occur.

Impacted Areas
View history, Documents tab for all documents.

Tested Areas

  1. View history for documents that are in progress or have been completed.
  2. View history for documents, considering all E-signature statuses.
  3. Documents tab.
  4. Download documents from the document tab.
  5. Validate whether an alert message is displayed when attempting to download a document with an expired token.

Issue: When uploading a document to the documents section, it does not get added, and the screen displays a continuous buffering symbol. However, the document eventually appears in the audit trail after some time.
Tracking Code: TAPSUP-7400
Case Number: 2023-0919-7989814
Reported Version: 1.14.3.0
Workaround
None

Pre-Requisites
Access to TAP Environment.

Steps to Reproduce

  1. Log in to the application.
  2. Search for a record.
  3. Go to the Documents section.
  4. Try uploading a document.

Expected Results of Steps
Documents should get uploaded successfully.

Actual Results of Steps
The document upload is unsuccessful, and the screen displays an endless buffering symbol. However, the document is observed to be successfully added to the audit trail.

Root Cause Analysis
This problem arises when a user uploads files and the user is subsequently deleted. When attempting to display files from a non-deleted user, an error log is generated.

Impacted Areas
Document upload in the Documents section.

Tested Areas

  1. Document upload in Document Action Menu.
  2. Document upload for Deleted Users.
  3. Document upload for Inactive/locked Users.
  4. Ensure that the console error log does not appear during testing.