TAP 1.22.4 Release Notes

Release Summary

The TAP 1.22.4 release includes new features, key bug fixes, internal defects, and known issues for a better user experience.

New Feature(s)

A new checkbox labeled "Apply default Role Rank to new SSO users" is now available under Admin → New User Settings, within the Default Role for New Users subsection. This feature allows administrators to control the Role Rank assigned to new users created via SSO.

Description:

• If the checkbox is checked, any new user account created via SSO will automatically receive the system-defined Default Role Rank. The assigned Role Rank value must match the current default.
• If the checkbox is unchecked, new users created via SSO will be assigned a Role Rank of 0, regardless of the system default.

The system's behavior for existing users and existing SSO configurations remains unchanged unless the checkbox is manually enabled. No existing users or Max Rank values are altered by this feature.

For more information, refer to the Role Ranks page.

Bug Fixes 

Issue: Duplicate requests were created in the dashboard, resulting in multiple statuses being displayed. Now, a single request is created, reflecting only one status.
Case Number: 2024-0219-8151434
Impacted Areas
Submit workflow

---

Issue: The downloaded file name was different from the original file name in the content library. The file name now remains the same as the original when downloaded.
Case Number: 2025-0311-8533580
Impacted Areas
Content Library

---

Issue: The endpoint previously generated an error when running API requests with URLs. The endpoint now successfully connects and accepts requests with any URL.
Business Automation → Pinned Filter Setup

WorkflowDashboard configuration for Available Dynamic Columns now restricts the use of special characters. Only the underscore (_) is allowed when creating or updating (saving) configurations.
Case Number: 2025-0227-8522112
Impacted Areas
API Connectivity/Endpoint Configuration

---

Issue: Previously, workflows would fail to proceed when a file name exceeded 95 characters, due to DocuSign’s filename length limitations. This issue has now been resolved, and workflows with e-signature enabled can successfully process files with names up to 100 characters.

To enhance user experience and provide clarity, a message will now be displayed beneath the e-Signature Template Sources table in the Template tab of the e-Signature Support section. This message will inform users that file names exceeding 100 characters will be automatically truncated to 100 characters before submission.

Case Number: 2025-0417-8572881
Impacted Areas
Workflow template file name

---

Issue: The user was previously assigned the new role without an updated rank, which remained at 0. This issue has been resolved, and now the user is assigned the role with Rank 255 and MaxRank 255 at the database level.
Case Number: 2025-0324-8546188
Impacted Areas
Role Rank

---

Issue: Previously, when using a Grid Datasource, searches did not return results containing special or accented characters (e.g., “_”). However, manually configured options worked as expected and included such characters. This has now been resolved and typing a term in the dropdown search correctly displays all matching results, including entries with special and accented characters.
Case Number: 2025-0523-8611822
Impacted Areas
Grid Datasource

---

Issue: When a user adds an entry to the datasource, saves it, exits the page, and then re-enters, the datasource previously appeared empty after reloading. This issue has been resolved, and the datasource now displays the latest data correctly.
Case Number: 2025-0605-8625257
Impacted Areas
Grid Datasource

---

Issue: A record could not advance to the next stage due to a submission error triggered by a file upload field, even though the field was not referenced by document generation or eSignature. This issue has been resolved so that non-referenced file upload fields no longer cause submission errors.
Case Number: 2025-0606-8625907
Impacted Areas
File Submit 

---

Issue: Previously, users could enter invalid dates (e.g., adding extra numbers in MM/dd/yyyy) or select dates outside the allowed range, and these values would still display on the dashboard. This has now been resolved with new DatePicker validations.

• Invalid date formats now show an error message with the correct format (e.g., “Date is not valid, date must match format dd MM yyyy”).
• If a date range is configured in the workflow, entering a date outside this range will show an error with the allowed range (e.g., “Date must be in a valid range between 06/26/2025 and 07/26/2025”).
• A new “Validate Date” option is available in field settings (enabled by default for new fields, off for existing ones unless updated).

Case Number: 2024-1122-8442089
Impacted Areas
Date field 

---

Internal Fixes

Issue: Previously, when users entered dates with ordinals (e.g., July 2nd, 2025), the datepicker misinterpreted the format and displayed incorrect values such as August 19n19, 2025, causing submission errors. This issue has been resolved, and dates with ordinals are now properly validated. To prevent errors, invalid formats that the datepicker cannot process are rejected.
Impacted Areas
Date field

---

Issue: Previously, text was displayed along with the selected value for the 'Grid External Data Source' in the audit trail. This issue has been resolved, and now only the selected value for the 'Grid External Data Source' is displayed in the audit trail.
Impacted Areas
Audit Trail

---

Issue: In the grid data source, when a user searched for any dropdown value using its lowercase reference, the results were not displayed. This issue has been resolved, and now the results are displayed regardless of case sensitivity.
Impacted Areas
Grid Datasource

---

Issue: The workflow submission previously did not display an error message on the Thank You page when an incorrect date format was entered. Now, an error message is displayed whenever an invalid date format is entered.
Impacted Areas
Date format

---

Issue: In the form mapping section, editing the existing mapping previously caused Grid Datasource values to not display in both the parent and child dropdowns. This issue has now been resolved, and the values are displayed correctly.
Impacted Areas
Form Mapping

---

Issue: In the View Condition pop-up, the condition values were previously blank when the Grid Data Source option was configured in a Custom HTML field. This issue has now been resolved, and the values are displayed correctly.
Impacted Areas
Condition pop-up

---

Issue: The downloaded file name included the file extension inappropriately, differing from how it appears in the Content Library. The file name extension is being duplicated, resulting in filenames like document.pdf.pdf and document.docx.docx. The file name matches the original display name without unnecessary extension details when downloaded.
Impacted Areas
Content Library

---

Issue: In Business Automation → Pinned Filter Setup, adding a file name with special characters previously saved without displaying an error. This has been resolved, and the configuration now validates file names and only allows the underscore (_) as the special character, displaying an error for any other special characters.
Impacted Areas
File Name

---

Known Issues

1. When downloading .txt and .css files from the Content Library, the downloaded file name may appear as an ID instead of the original file name. 
2. eSignature submission fails when a form field value (text or textarea) exceeds the maximum length of the corresponding text field mapped in the eSignature document. This issue occurs with the DocuSign provider but not with the Adobe eSignature provider. 
3. Files with names containing 212 characters cannot be uploaded, even though the maximum allowed file name length is 255 characters (including the extension). 
4. In form preview, if a user enters two extra numeric characters in the date field and then clicks elsewhere on the screen, the selected date is cleared from the field. 
5. For fields with currency validation and a MaxSize of 12, entering more than 12 digits highlights the field in red and blocks form submission without showing an error message, leaving users unclear about the input issue.