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.5.1 & 1.5.2 Release Notes

Feature Enhancements

Blank Currency Value:

Users can now select a blank value when using a currency validated field that is configured to allow the selection of currency type. This allows users to ‘Clear’ the field entirely if a currency is selected on accident.

 

Pinned Filter ‘Delete’ Action Moved:

Users can no longer delete site wide pinned filters directly from the dashboard view. Instead, this action is now controlled by admins with access to the generic grid configuration section. Users can still delete pinned filters that they created for themselves directly from the dashboard view.

 

‘Users’ Page Includes Active/Inactive Status:

The ‘Users’ page in Administration has been updated to display a User’s status. A new column has been added to display this.

 

Bug Fixes

Issue: Reminder prefix in subject line of emails initiated via API
Tracking Code: TAPSUP-2398
Salesforce Case Number: 2020-1111-697610
Expected Result: Next Action notifications for workflows triggered through the API will no longer have the ‘Reminder’ prefix attached, unless they are true Reminder Emails.

Issue: Authorization/Privacy - Bypass Read Privacy
Tracking Code: TAPSUP-2634
Salesforce Case Number: 2020-1111-697610
Expected Result: Security update to prevent email querying through API.

Issue: Prepopulation rules(using a datasource) failing after Import
Tracking Code: TAPSUP-3136
Salesforce Case Number: 2021-0325-759411
Expected Result: Grid Prepop rules will no longer fail after a workflow from older release has been imported to new environment.

Issue: Docs are no longer base64 encoded
Tracking Code: TAPSUP-6953
Salesforce Case Number: N/A
Expected Result: Fix for issue that caused docs being sent through the API to be URL encoded instead of Base64 encoded. When using the API to send docs from tap, the ‘:content::’ will send a base64 encoded document.

 

  • Was this article helpful?