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

  1. Last updated
  2. Save as PDF
This page provides an overview of the new features being incorporated into the 1.16.5 release.

Defects

Improved Accuracy in Date Completed Calculation:

We've enhanced the Date Completed feature to ensure accuracy by recalculating only when the request reaches an end-stage. Previously, the Date Completed was calculated with every relationship and stage submission, leading to inaccuracies for incomplete requests. Now, Date Completed reflects the true completion date only for completed workflows, eliminating any discrepancies in date values for incomplete workflows. 

Impacted Areas: In the Analytics page, within the widgets' DateCompleted columns, only the date format is displayed, excluding the time component.

Tested Areas: 

  1. Scenarios for completing a simple workflow.
  2. Scenarios for completing different parallel workflow configurations.
  3. Scenarios for completing a simple workflow with looping.

For more information on Analytics 2.0, refer to the Client Success Center.

Tracking Code: TAP-28772

Enhanced Workflow Completion Time Calculation

We've refined the calculation of workflow completion time to ensure accuracy and reliability. Previously, the complete time was calculated at every stage status update, leading to potential inflation in completion time, especially in Sisense calculations. With this enhancement, the complete time now accurately reflects the total time taken to complete the workflow, calculated only once the workflow reaches its final status. This improvement ensures that the reported completion time aligns precisely with the actual workflow completion. 

Impacted Areas:  The TimeToCompleteWorkflow column within the widgets section on the Analytics page.

Tested Areas: 

  1. Scenarios for completing a simple workflow.
  2. Scenarios for completing different parallel workflow configurations.
  3. Scenarios for completing a simple workflow with looping.

For more information on Analytics 2.0, refer to the Client Success Center. 

Tracking Code: TAP-28736

Improved TimeSpentOnStatus Calculation for Parallel Pathways 

Previously, when a workflow followed a parallel pathway, the timespentonstatus calculation was inaccurate, merging all parallel stages into a single relationship. Rather than computing after each stage within the parallel pathway was submitted, it calculated after the last stage in all parallels, resulting in combined data points. This enhancement ensures that for parallels, TimeSpentOnStatus, and TimeSpentStatus, calculations occur after each stage submission, recording time data points for individual statuses within parallel branches. 

Impacted Areas:  The TimeSpentOnStatus column within the widgets section on the Analytics page.

Tested Areas: 

  1. Verified time spent on status, calculated in minutes.
  2. Confirmed time spent on the entire workflow, calculated in hours.
  3. Tested simple workflow scenarios.
  4. Tested parallel workflow configurations.
  5. Ensured accurate time calculation for all relationships.
  6. Validated time calculation for the last token.
  7. Tested workflows with back-and-forth stages.
  8. Verified time calculation for conditional workflows.
  9. Tested multi-stage workflows for accurate time tracking.

For more information on Analytics 2.0, refer to the Client Success Center. 

Tracking Code: TAP-29746

Bug Fixes

Issue: API Call not taking custom error message when triggered at stage level. 

Tracking Code: TAP-32031

Case Number: N/A

Reported Version: 1.15.0

Workaround

None

Pre-Requisites

  • Workflow with API Call configured at the stage level.
  • Custom error message configured in the validation section of that API call.

Steps to Reproduce

  1. Create a workflow stage.
  2. Add a button field and configure an API call linked to the button field.
  3. Add validation to that API call and include a custom error message for when the call is not valid.
  4. Run the workflow and trigger the API call that will result in a non-valid call.

Expected Results of Steps

The configured custom error message should be displayed in the error message popup.

Actual Results of Steps

No errors appear in the error message popup.

Root Cause Analysis

The exception's error message order was incorrect, and there was a missing Json Property Attribute for a class member.

Impacted Areas

Triggering a call at the stage level.

Tested Areas

  1. External API usage at stage
  2. External API usage at relationship level
  3. Custom error setup on multiple API calls
  4. Testing without custom error setup
  5. Testing without validation rules

Issue: External API throws an error if the exact response is not received. 

Tracking Code: TAP-32386

Case Number: N/A

Reported Version: 1.15.0

Workaround

None

Pre-Requisites

Workflow configured with an API call that retrieves information for a TAP Form.

Steps to Reproduce

  1. Create a multistage workflow.
  2. Add 2-3 text form fields.
  3. Configure an API call on the first relationship.
  4. Map the values from the response of the API call to the text fields.
  5. Run the workflow and trigger the API call so that it returns only 1-2 of the 3 mapped responses.

Expected Results of Steps

If the call is successful, mapped responses should be sent to the TAP fields. If certain values are absent in the response, the corresponding mapped field should remain empty.

Actual Results of Steps

The workflow encounters an error when it reaches this API call.

Root Cause Analysis

Parsing the JSON alias of the External API configuration lacked proper conditions.

Impacted Areas

Triggering a call at the stage level.

Tested Areas

  1. External API usage at stage
  2. External API usage at relationship level
  3. Custom error setup on multiple API calls
  4. Testing without custom error setup
  5. Testing without validation rules

Issue: External API call gets saved twice in audit trial when clicked on Save Button. 

Tracking Code: TAP-32749

Case Number: N/A

Reported Version: 1.15.9

Workaround

None

Pre-Requisites

  • Access to the TAP application.
  • Any API URL for GET.

Steps to Reproduce

  1. Import the workflow.
  2. Ensure that External API is configured for Stage 1.
  3. Publish, save, and preview the workflow.
  4. Confirm that there is no summary tab as no updates occur at Stage 1.
  5. Click on the "Button."
  6. The External API call will be made and will fail.
  7. An error warning will be displayed with a count of 1.
  8. Click on "Save."
  9. Navigate to the Summary.
  10. Expand the Stage 1 update.
  11. Verify that the stage update reflects only one API call trigger.

Expected Results of Steps

The External API call should be triggered only once and reflected in the stage update.

Actual Results of Steps

The External API call is triggered twice and appears twice in the stage update.

Root Cause Analysis

When saving stages, the system retrieves all audit trial details associated with a button field. After multiple saves, it redundantly stores the audit trail details, leading to duplicate entries in the audit logs.

Impacted Areas

Saving the stage.

Tested Areas

  1. Stage Update functionality
  2. All Button Trigger Check
  3. Audit Trial Check

Issue: The document is not getting deleted when we "delete" the document in the signature repository. 

Tracking Code: TAPSUP-7139

Case Number: 2023-0714-7911651

Reported Version: 1.14.3.0

Workaround

None

Pre-Requisites

Access to TAP Docusign.

Steps to Reproduce

  1. Navigate to the Signature Repository within the Document Library.
  2. Click on the "Actions" dropdown menu and select "Delete" for any document.
  3. A dialog box saying “Document has been deleted” will appear.
  4. Refresh the repository, and despite the deletion confirmation, observe that the document remains listed, indicating it was not deleted as expected.

Expected Results of Steps

The document should be removed upon selecting the "Delete" option from the Actions dropdown.

Actual Results of Steps

The document remains in place despite attempting to delete it from the signature repository.

Root Cause Analysis

The status is failing to update due to issues with the services, and adjustments have been made to the messages displayed to end users.

Impacted Areas

Record is deleted from the Signature Repository.

Tested Areas

Record is deleted from the Signature Repository.

Issue: Cannot Download Dashboard Filter Due to Errors in RIF57393 and RA52917 on production. 

Tracking Code: TAPSUP-8137

Case Number: 2024-0202-8133660

Reported Version: 1.15.9.1

Workaround

None

Pre-Requisites

Access to the TAP application.

Steps to Reproduce

  1. Navigate to the default production environment.
  2. Submit the Workflow using the text containing special characters in the 'Description of Product or Service' field.
  3. Try to export the request from the dashboard.
  4. An error processing request will be displayed.
  5. Remove the content from the 'Description of Product or Service' field on the dashboard to successfully export the file.

Expected Results of Steps

When "Description of Product or Service" is included, the file should export without encountering any errors.

Actual Results of Steps

An error is encountered when including the field "Description of Product or Service."

Root Cause Analysis

This issue occurred due to the presence of hexadecimal characters in the workflow record data.

Impacted Areas

Workflow Dashboard export.

Tested Areas

  1. Workflow dashboard export with SP and Linq.
  2. Dynamic columns with hexa characters.
  3. Records with special characters.

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Topic
  2. Tags
    1. 1.16.4
    2. 1.16.5
    3. TAP 1.16.4