Skip to main content
Mitratech Success Center

FAQs and Solutions

This section details frequently reported items and their workarounds or solutions.

In Workflows Initiated via API, First Email May Contain "Reminder" in Subject Line

If a workflow has an email reminder on the first relationship and it is initiated via an API call, the very first email sent has the prefix "Reminder" in the subject line and is inconsistent with the behavior of workflows not initiated via API. 

If you would like to be notified when this is addressed in a release please submit a case to Mitratech Support and reference TAPSUP-2398.

Error Received When Uploading file with Multiple "." via Attachments on the Workflow Form

Files named with multiple "." (ex. Test12.11.20) can be uploaded in a form field but not when using the Attachments section in a workflow request. Error "Multiple extensions are not allowed." will occur. 

Alternate Options: Upload file via form field or remove period from file name. 

If you would like to be notified when this is addressed in a release please submit a case to Mitratech Support and reference TAPSUP-2725.

Searching SFDC Returns only 20 Results

Search field returns only top 20 results.

If you would like to be notified when this is addressed in a release please submit a case to Mitratech Support and reference TAPSUP-2418.

Workflow ID not Displayed in Custom HTML Field both as Text and HTML

1) Create 2 forms. Second form should have the custom HTML field in which we try to display the workflow ID.
2) Create a sequence generator and add to the workflow. Check the box use ID as workflow name
3) Assign the first form to first stage and second form to second stage. Provide appropriate form access.
4) Preview workflow. When the request moves to second stage, workflow ID must be displayed . But if workflow ID is displayed as HTML field, value is null and if workflow ID is displayed as text, it is displayed as { {sequenceId::_workflowid} } and not the value.

Alternate Solution is to send workflow ID as a part of the email notification. 

If you would like to be notified when this is addressed in a release please submit a case to Mitratech Support and reference TAPSUP-2592.

Multi-Select Docs do not attach to Email Notifications after Splitter Stage Is Used

Documents added via a multi-select form field are not included in the merged document. To resolve, add a temporary stage after the splitter and manually submit. 

If you would like to be notified when this is addressed in a release please submit a case to Mitratech Support and reference TAPSUP-2039.

Unable to Import Workflow

At times a user can experience a failure with importing templates from one environment to another and no errors ar displayed in the user interface. Checking the Browser Console logs reveals an "Uncaught TypeError" thrown by the updateUserDropdownsBeforeImport method. To resolve, open the Open the .tapw file in a text editor, search the file for the string, and remove all instances: "Verification":"users",

If you would like to be notified when this is addressed in a release please submit a case to Mitratech Support and reference TAPSUP-2641.

TAP External API Inserts Alternate Workflow Name into Request Body

Records in the dashboard and requests in the API call are named differently when using the TAP External API, meaning that the friendly names do not match and make it difficult for users to cross-reference requests between systems. 

If you would like to be notified when this is addressed in a release please submit a case to Mitratech Support and reference TAPSUP-2684.

Using Quick Submit Feature Submits Stages Twice

A workflow that has an email notification quick-submit feature may at times be submitted twice after submitting with the quick submit feature. Downstream stages will also be submitted twice. 

Workaround: Remove quick submit email feature. 

If you would like to be notified when this is released please submit a case to Mitratech Support and reference TAPSUP-2132.

SSO Cycling When Using Safari

When logging in via Safari with SSO activated the user may be cycled back out of the application. To resolve set the Safari cookie setting to "Always Allow". If this does not resolve the cycling se the Safari cookie setting to "Allow from websites I visit" & add Okta in the list of websites.

Workflow Permissions

We have also received several cases for disappearing permissions which were the result of reverting to an earlier version of the workflow and not re-adding permissions. Make sure that after reverting to a previous version permissions are checked before going live. 

Dashboard Values Empty for Fields

Database shows form field data entered and stored, but it is not updating the dashboard. this is currently corrected via script. A permanent solution is under development. If you would like to be notified when this is released please submit a case to Mitratech Support and reference TAP-2694.

Must Clear Cookies to use TAP with Safari and SSO

SSO authentication will continue to loop in Safari and fails to redirect to TAP unless the browser cookies and cache are cleared.

Solution:

1) Set the Safari cookie setting to "Always Allow". 

2) If  Step1 does not work, then Set the Safari cookie setting to "Allow from websites I visit" & add SSO provider in the list of websites.

 

 

  • Was this article helpful?