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

  1. Last updated
  2. Save as PDF

Bug Fixes

Issue: Pending to send to e-sign status doesn't show in the signature repository
Tracking Code: TAPSUP-7062 
Case Number: 2023-0627-7893412
Reported Version: 1.14.3.0
Workaround
None

Pre-Requisites
Access to a TAP environment.

Steps to Reproduce

  1. Create an e-signature (Docusign) workflow by choosing to submit the interactive option and save. 
  2. Preview the workflow and submit the request.
  3. Once the request is completed you will see the preview document option.
  4. If you choose to, you can exit or close the window without previewing and then resubmit the document.

Expected Results of Steps
After closing the page without submitting the document, the eSignature document status within the dashboard appears as 'Pending to Send to eSign.' This identical status should also be reflected in the 'Signature Repository.'

Actual Results of Steps
After closing the page without submitting the document, the eSignature document status within the dashboard displays as 'Pending to Send to eSign.' However, in the 'Signature Repository,' the current status is 'Out for Signature,' which is not the expected behavior.

Root Cause Analysis
This problem was due to the status not being saved. The issue is resolved with TAP-27452.

Impacted Areas

  1. e-Signature support in DocuSign 
  2. Documents tab 
  3. View history 
  4. Signature repository 
  5. Workflow submission page  
     

Tested Areas

  1. E-signature 
  2. Callback 

The changes are completed as part of TAP-27452.


Issue: Data from address fields in TAP is not getting mapped to Team Connect address fields.
Tracking Code: TAPSUP-6743
Case Number: 2023-0425-7769436
Reported Version: 1.13
Workaround
None

Pre-Requisites

  1. TAP Staging environment
  2. Access to TAP and TeamConnect instances

Steps to Reproduce

  1. Import the Workflow.
  2. Load the workflow.
  3. The Contact field is pulled from TeamConnect to TAP through the TeamConnect setup.
  4. Selecting the Address type is mandatory.
  5. Street address, city, pin code, and state are configured and the data should be mapped to Team Connect contact through mapping.
  6. Preview the workflow and run a test by selecting a contact.
  7. Provide address information.
  8. Submit the workflow.
  9. The data is visible in the audit history.

Expected Results of Steps
The data from the address fields will be mapped to the corresponding address fields in TeamConnect.

Actual Results of Steps
The data from the address fields is not getting mapped to the corresponding address fields in Team Connect.

Root Cause Analysis
Previously, TeamConnect used a text box for the "country" field, but it has transitioned to use a lookup table. Consequently, the field "contAddress.Country" is now obsolete and should be eliminated from the TAP UI.

Impacted Areas

  1. Obsolete field contAddress.country from the TAP-TC system fields.
  2. The country field in TeamConnect and country fields that are configured using TeamConnect lookup must be mapped to the TeamConnect country for addition and update.
  3. Multiple Add or update.

Tested Areas 

All address fields in TeamConnect.


Issue: This field is required and appears only for TeamConnect list-driven drop-down fields but not TAP data source dropdown fields. 
Tracking Code: TAPSUP-6379
Case Number: 2023-0127-7637508
Reported Version: 1.11.0.1
Workaround
None

Pre-Requisites
Access to a TAP Environment.

Steps to Reproduce

  1. Preview the workflow.
  2. Do not fill in the fields for TAP and TeamConnect data sources.
  3. Submit the workflow.

Expected Results of Steps
The red text "This field is required" is to be displayed when the TAP and TeamConnect data sources drop-downs are left unfilled.

Actual Results of Steps
The red text appears under the TeamConnect data source drop-down even prior to submission, exclusively below the TeamConnect drop-downs and not the TAP drop-downs.

Root Cause Analysis
When populating options for selection during page load, any changes made, trigger a change event. If the selection is left empty, a required message is shown.

Impacted Areas

  1. Multiple TeamConnect fields
  2. TeamConnect fields Configuration in designer
  3. Conditions, mappings, document building, and formulas
  4. Multiple stages
  5. Submit and Save buttons

Tested Areas
All the below fields as required and optional fields.

  1. Multiple TeamConnect fields
  2. TeamConnect fields Configuration in designer
  3. Conditions, mappings, document building and formulas
  4. Multiple stages
  5. Submit and Save buttons
  6. Drop Down, Multi Select, TeamConnect Record Search, TeamConnect Categories

     

Issue: Dashboard Export with Unicode Characters  
Tracking Code: TAPSUP-7314 
Case Number: 2023-0821-7955423
Reported Version: 1.14.3.0
Workaround
None

Pre-Requisites
Access to a TAP Environment

Steps to Reproduce

  1. Import the workflow.
  2. Input the data to the 'Area' field and submit the data.
  3. Add the dynamic field 'Unicode' to the dashboard and try to export.

Expected Results of Steps
The dashboard should be exported without encountering any issues.

Actual Results of Steps
The dashboard is not downloaded and displays an error that says 'Error Processing Request'.

Root Cause Analysis
This problem arose because non-standard hexadecimal characters were added to a form. When attempting to export this data from the dashboard, the OpenXml library (a third-party tool for generating Excel files) generates an error.

Impacted Areas
Data export from the dashboard.

Tested Areas

  1. Dashboard export with dynamic columns
  2. Dashboard export with only static columns
  3. Both types of columns
  4. Empty dynamic columns
  5. Complex dynamic column data
  6. LINQ and Stored Procedures

     

Issue: TextField in Workflow using validate Social Security Number input displays encrypted field
Tracking Code: TAPSUP-7821 
Case Number: 2023-1103-8043279
Reported Version: 1.15.7.0

Workaround
None

Pre-Requisites
Access to a TAP environment    

Steps to Reproduce

  1. Add a text form field to your workflow.
  2. Add SSN validation to the form field.
  3. Fill in SSN value in the form and submit the workflow.
  4. Go to the audit trail and view SSN value.
  5. If SSN value is used in a later stage, go to the stage and view displayed SSN value.

Expected Results of Steps
When viewing the audit trail, the SSN submitted by the user should display.

When using the SSN value in a later stage of the workflow, the SSN submitted by the user should display.

Actual Results of Steps
You will see an encrypted value for the SSN.

Root Cause Analysis
When a TextField is marked to Validate Social Security Number, it undergoes a change in its database storage process. The value gets encrypted before saving it to the database. Subsequently, to display the value in the form, it needs to be decrypted. The error is on the decryption. 

Impacted Areas

  1. Form field with SSN validation.
  2. SSN value displayed in later stages.
  3. SSN value in audit trail.
  4. Notification when the form field is added.
  5. E-signature document by adding tags for that form field
    Formula.
  6. Form field on external API request.

Note: Here, form field means the field which is configured for SSN validation.

Tested Areas

  1. Form field with SSN validation
  2. Multiple stages with SSN value displayed
  3. Workflow audit trail
  4. Notifications
  5. Document
  6. View History
  7. Edit request
  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Classifications
    This page has no classifications.
  2. Tags
    1. 1.15.9.1
    2. 1.15.9.1 patch release notes
    3. 1.15.9.1 release notes