TAP 1.19 Release Notes
Production Date: 11-08-2024
Release Summary
TAP 1.19 release includes technical maintenance such as library upgrades and remediation of security vulnerabilities, Kendo UI fixes, and Bug fixes for a better user experience.
Technical Maintenance
- Library upgrades
- Security enhancements
Kendo UI Fixes:
- UI Enhancements: Upgraded Kendo UI version improving the user interface and experience.
- Document Library Drag-and-Drop Issue: Resolved alignment issues with drag-and-drop in split-screen mode.
Bug Fixes:
- Auto Submit API Issue: Fixed an issue where 'Auto Submit' failed when using an external API in workflow stages.
- Mentioning Users in Collaboration Forms: Resolved issues with '@' mentions not displaying user names correctly.
- TeamConnect Key Retrieval Issue: Fixed an error where TeamConnect values were not being retrieved, causing category update failures.
Kendo UI Fixes
The Kendo UI version in TAP has been upgraded bringing changes to the user interface (UI) and enhancements to the user experience.
Issue: Drag and Drop Upload Overlapping and Alignment are not displaying properly in the Document Library when the browser is kept on split screen.
Tracking Code: TAP-38673
WorkaroundThe
None
Pre-Requisites
Access to TAP
Steps to Reproduce
- Split the browser window.
- Navigate to Document Library > Document Library.
- The drag-and-drop alignment is not displaying correctly.
Expected Results of Steps
The drag-and-drop upload feature in the Document Library has no overlapping or alignment issues when the browser is in split-screen mode.
Actual Results of Steps
When the browser is in split-screen mode, the drag-and-drop upload feature in the Document Library is overlapping, and the alignment is not displaying correctly.
Resolution
The issue with the drag-and-drop upload feature in the Document Library, where overlapping and alignment problems occurred in split-screen mode, has been resolved. It is now functioning as expected, with no overlapping or alignment issues.
Root Cause Analysis
Kendo Upgrade
Impacted Areas
Document Library with both split screen and full screen
Tested Areas
- Verified in the Document Library with both split screen and full screen
- Multiple browsers in split-screen mode and while resizing the screen
- Multiple devices such as iPad and Mac
- Different screen resolutions and sizes
Issue: Pinned filter setup hovering over on Select in the Actions it’s color is not getting changed.
Tracking Code: TAP-39893
Workaround
None
Pre-Requisites
Access to TAP
Steps to Reproduce
- Navigate to Business Automation > Pinned Filter Setup.
- Select Archive Library from the dropdown menu.
- Hover the mouse over the Select option under Action.
- The issue will be replicated.
Expected Results of Steps
In the pinned filter setup, hovering over the Select option in the Actions should change its color.
Actual Results of Steps
In the pinned filter setup, hovering over the Select option in the Actions does not change its color.
Resolution
The issue where hovering over the Select option in the Actions of the pinned filter setup did not change its color has been resolved. It is now functioning as expected, with the color changing upon hover.
Root Cause Analysis
Kendo Upgrade
Impacted Areas
Pinned Filter Action column
Tested Areas
- Verified that the color changes upon hovering in the Pinned Filter Action column.
- Functionality across multiple browsers.
- Grid across multiple pages.
Issue: Wrong string is showing when the file is not uploaded on Content Library File upload.
Tracking Code: TAP-47092
Workaround
None
Pre-Requisites
Access to TAP
Steps to Reproduce
- Navigate to the Content Library page.
- Upload a file that is not supported.
- Verify the issue with the validation message.
Expected Results of Steps
An appropriate message should be displayed upon file upload failure.
Actual Results of Steps
An incorrect message is displayed when a file fails to upload in the Content Library.
Resolution
The issue where an incorrect message was displayed upon file upload failure in the Content Library has been resolved. Now, the appropriate message is correctly shown when a file fails to upload.
Root Cause Analysis
Kendo Upgrade
Impacted Areas
File Upload in Content Library
Tested Areas
- Verified the error message when files fail to upload.
- Checked other areas where file uploads are possible.
- Ensured the error message does not display "successfully uploaded" when the file fails to upload.
- Multiple file types, including PDF and DOC.
Bug Fixes
Issue: Auto submit is not working when the external API is configured to the stages.
Tracking Code: TAPSUP-9483
Case Number: 2024-0416-8216531
Reported Version: TAP 1.17.1
Workaround
None
Pre-Requisites
Access to TAP
Steps to Reproduce
- Import the workflow.
- Save and preview the workflow.
- Set auto-submit with a 2-minute delay and configure the external API for the 'Drafting documents' stage.
- Requests remain stuck at the 'Drafting documents' stage.
Note: Auto-submit fails when the external API is configured for the stages.
Expected Results of Steps
The ‘Auto Submit’ should function correctly if the external API is configured for the drafting documents stage.
Actual Results of Steps
Auto Submit is not functioning when the external API is configured for the 'Drafting documents' stage, making requests stuck.
Resolution
The issue where 'Auto Submit' was not functioning correctly and requests got stuck when the external API was configured for the 'Drafting documents' stage has been resolved, and it now functions correctly.
Root Cause Analysis
This issue occurred due to the use of the Auto Submit delay. While processing the response file from the External API, we encounter null exceptions in the logs.
Impacted Areas
Auto Submit function
Tested Areas
- External API functionality
- External API set with files as a response
- Different types of form access for file and multi-upload fields used in External API functionality
- External API set with files as a response in the following scenarios:
- Auto Submit
- Normal Submit
- Auto Submit Delay
- Callback
- Initiate Workflow call
Issue: User cannot access the collaboration form when ‘@’ is mentioned.
Tracking Code: TAPSUP-9478
Case Number: 2024-0716-8305795
Reported Version: TAP 1.17.7
Workaround
None
Pre-Requisites
- Access to TAP
- Ensure that your workflow includes a collaboration stage and that there is a user email account containing an apostrophe.
Steps to Reproduce
- Create or import the workflow.
- Launch the collaboration stage in the workflow.
- In the discussion section, ‘@’ mention the user email address that contains an apostrophe.
Expected Results of Steps
The user's name is highlighted in blue.
Actual Results of Steps
The user's email doesn't appear; instead, the full email address is shown, and it's not highlighted.
Resolution
The issue where the email does not appear when @ is mentioned has been resolved, and now the user's name is highlighted in blue.
Root Cause Analysis
HTMLEncode was applied to prevent HTML injection. However, HTMLDecode was not applied when retrieving the mentioned user's email.
Impacted Areas
Mentioning the User in Collab discussion
Tested Areas
- Mentioning the User in Collab discussion both comments and replies
- HTML Injection
- Add and Edit comment
- Audit Trail, Edit Request
Issue: After selecting the TeamConnect fields to update categories, the TeamConnect key is not pulling values. Unable to retrieve TeamConnect values to TAP using this TeamConnect key.
Tracking Code: TAPSUP-9637
Case Number: 2024-0627-8287077
Reported Version: TAP 1.17.9
Workaround
None
Pre-Requisites
Access to TAP
Steps to Reproduce
- Log in to TAP.
- Navigate to the workflow, select the "TC Setup" field, and configure the TeamConnect options.
- While adding categories, an error popup appears: "There was an error pulling the TeamConnect data, please check your TeamConnect key."
Expected Results of Steps
After selecting the TeamConnect fields to update the categories, the values should be refreshed accordingly.
Actual Results of Steps
After selecting the TeamConnect fields to update the categories, the TeamConnect key is not retrieving values. Unable to pull TeamConnect values into TAP using this key.
Resolution
The issue where the TeamConnect key was not retrieving values has been resolved. Now, after selecting the TeamConnect fields to update the categories, the values are successfully retrieved using the TeamConnect key. The data is correctly pulled into TAP, and the categories are updated as expected.
Root Cause Analysis
The TAP code contains a hard-coded decoding mechanism for the TeamConnect Key. As part of this process, the number '36' is being incorrectly replaced with the symbol '$'.
Impacted Areas
TeamConnect Key
Tested Areas
- TeamConnect functionality
- TeamConnect fields, TC Record field, and Category fields
- Dropdown mapped to TeamConnect functionality
- Multiselect options mapped to TeamConnect functionality
- Form-level testing and configuration testing related to TeamConnect