TAP 1.6 Release Notes
Feature Enhancements
File Size and Type Enhancements: As a workflow designer, you are now able to configure allowed file types, file name character limits, and allowed file sizes (up to 100 MB) for file upload form fields. The ability to set these options adds additional validation for files, especially when files are passed to applications with file requirements of their own via TAP (i.e. eSignature, Salesforce, etc.). For more information see File Upload and Multi Upload on the Client Success Center.
Form Mapping with Boolean Checkbox: Automatically check or uncheck a checkbox field based on the value of a another field, as well as, automatically populate values of fields based on the value of a checkbox field. See Form Mapping for more information.
Document Builder: When 'Send without eSign' is checked and multiple docs are attached to relationship, all .docx files are merged into a single file. Navigate to 'Send without using eSignature" to learn more.
External API: When copying values from area fields to text fields using formulas, carriage returns and/or spaces are no longer stored in the database and the value complies with JSON formatting in order to be used in external API calls.
Form result values can now be used for basic authentication on an API call. For more information see external API.
Audit Trail Enhancements: When a user cancels a record using the 'Cancel' Action on the Dashboard, both the time stamp of when it was canceled and the user who canceled it are recorded in the record's audit trail.
Role/Department Pre-population: You can now populate a User’s TAP Role or Department into a workflow field by using a pre-population rule based on Current User or User Select Dropdown.
API Endpoints: New API endpoint that allows user to send form field data to an in progress workflow without needing to submit the current stage. For more information see TAP APIs.
Document Field Type: Update Document Fields with contents of other document fields or the contents of a built document using form mapping. This can be triggered with or without a parent value.
The Document Field Type can now be used as a destination field for documents of type .doc or .docx sent to TAP via API.
Document Field Type content from multiple Document Fields can now be merged together using Form Result Values.
For more information see Document Field Type
Defect Fixes
Issue: Upon adding or editing a TC relationship an error is thrown.
Tracking Code: TAPSUP-2878
Salesforce Case Number: 2021-0129-726126
Expected Result: Error no longer thrown; resolved handling of null check.
Issue: Cannot create a company contact in TeamConnect when 2 or more conditions are mapped to a particular field
Tracking Code: TAPSUP-3127
Salesforce Case Number: 2021-0321-756917
Expected Result: TeamConnect company created
Issue: Unable to export the dashboard with filter for large values
Tracking Code: TAPSUP-2877
Salesforce Case Number: 2020-1117-699441
Expected Result: Call to export large values with a filter now loop rather than attempt to pull total records
Issue: When setting form access for a Custom HTML field, the field no longer has a label or any identifier and is simply blank.
Tracking Code: TAPSUP-2759
Salesforce Case Number: 2020-1229-710099
Expected Result: First line of the custom html field should display on form access
TAP 1.6.2
Issue: Signature field must be signed each time an edit is saved in collaboration stage.
Tracking Code: TAPSUP-3354
Salesforce Case Number: 2021-0526-785291
Expected Result: Form saves successfully upon "Save" without signing if it has already been signed
TAP 1.6.3
Issue: Unexpected errors when submitting a record in a workflow when field is set to hide based on condition
Tracking Code: TAPSUP-3477
Salesforce Case Number: 2021-0617-794839
Expected Result: No error
Issue: Workflow Requests sent to esignature in splitter not visible in dashboard
Tracking Code: TAPSUP-3475
Salesforce Case Number: 2021-0617-794790
Expected Result: Request visible in dashboard
TAP 1.6.5
Issue: Workflow Requests sent to esignature in spliter not visible in dashboard
Tracking Code: TAPSUP-3475
Salesforce Case Number: N/A
Expected Result: Records out for signature and post signing will be visible in dashboard to non Super Admins.
Issue: Password Reset Vulnerability
Tracking Code: TAP-7634
Salesforce Case Number: N/A
Expected Result: Fix for a security issue identified within the password reset API endpoint.