Upgrade(s)

JavaScript Library Security Upgrade: To strengthen the security of our web application, we've proactively upgraded JavaScript libraries to the latest versions. This ensures enhanced protection against potential threats and provides a more secure and reliable experience for our users.

Bug Fixes

Issue: The records from the deleted requester are moved to the Completed stage.
Tracking Code: TAPSUP-7223
Case Number: 2023-0720-7917630
Reported Version: 1.14.3.0
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

1. Create a simple workflow with stages assigned to the requester and another user role.
2. Initiate the workflow using a test user, making this test user the requester.
3. Delete the requester from the administration tab before the next stage is submitted.
4. Let the other user submit the second stage.

Expected Results of Steps
Once the second stage is submitted, the request should continue to the third stage and should not change the status to complete.

Actual Results of Steps
When the requester is inactive or deleted in TAP and the next stage is assigned to them, the request is automatically moved to the completed stage.

Root Cause Analysis
When a workflow is submitted, if the status transitions to a stage where the assigned user or role has been deleted, no token is generated for that stage. Additionally, the token for the submitted stage is also closed. As a result, with no active tokens present, the workflow is automatically closed, and no current assignee is displayed.

Impacted Areas
Workflow Submit

Tested Areas

1. Workflow Submit both Super Admin and non-super Admin
2. Deleting a single role/user and deleting multiple roles/users
3. E-Sign before deletion of the user
4. Collaboration stage
5. Dashboard Linq & SP
6. One round of the Anonymous user submission process
7. Reassign the workflow
8. Default Notifications data 

---

Issue: The client is unable to submit the record to the next stage.
Tracking Code: TAPSUP-9374
Case Number: 2024-0514-8243127
Reported Version: TAP 1.17.4.0
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

1. Log in to TAP.
2. Click on "Edit Request" for the record.
3. Click "Submit."
4. An error message will appear in the UI.

Expected Results of Steps
The client should be able to submit the record to the next stage.

Actual Results of Steps
The client is unable to submit the record to the next stage.

Root Cause Analysis
This issue occurs when a boolean datatype field in TeamConnect is mapped to a currency-validated field in TAP within the TeamConnect Support configuration. TAP is unable to correctly parse values with certain currency symbols (e.g., "£50.00", "€50.00", "¥50.00") due to missing culture information.

Impacted Areas

1. TeamConnect-TAP integration with Decimal TeamConnect Field datatype
2. Currency supported by TAP

Tested Areas

1. TeamConnect-TAP integration with Decimal TeamConnect Field datatype
2. Currency supported by TAP and all its formats

---

Issue: Drop-down using External Data Source does not display results after workflow changes are saved.
Tracking Code: TAPSUP-9410
Case Number: 2024-0613-8274609
Reported Version: TAP 1.17.7
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

1. Create a workflow with a dropdown, setting "Configure Options" to 'Use data source as option data' and selecting an 'external grid' data source. Click "Save."
2. Preview the workflow to confirm that the dropdown displays values from the grid data source.
3. Open the designer form while keeping the preview form open.
4. Save the designer form without making any changes.
5. Return to the preview form and click on the dropdown again.

Expected Results of Steps
The dropdown continues to display results even if a user is actively working on the workflow while the form is being filled out.

Actual Results of Steps
The affected dropdown does not display any results.

Root Cause Analysis
When the workflow is saved, new IDs are assigned to each form field in the database. If the form is used without reloading, the IDs for dropdown fields linked to an external data source may not align correctly. This ID mismatch can cause problems with the external data source URL, particularly if it includes filters or mappings, leading to the dropdown displaying ‘no results’.

Impacted Areas
External Grid Data sources

Tested Areas

1. External Grid Data sources 
2. External Grid Data Sources mapped dropdown with Autosubmit, APIs 
3. External Grid Datasources  pre-population and form mapping
4. External Grid Datasources with Child workflow and Collab stage

---

Issue: The values are getting changed automatically while scrolling the mouse on any form field settings like size, rows, etc in the Designer.
Tracking Code: TAP-50016
Case Number: N/A
Reported Version: None
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

1. Log in to the TAP application.
2. Navigate to Business Automation → Designer → Create.
3. Add form fields and review the Field settings.
4. Scroll through the Field settings, such as Size, Max Size, Rows, Columns, etc., for different form fields.

Expected Results of Steps
Mouse scrolling should not automatically change values.

Actual Results of Steps
Values in the form field settings within Designer are being changed by mouse scrolling.

Root Cause Analysis
This issue arises due to the browser's default behavior, where scrolling over many input fields automatically increases or decreases the values.
Note: Since mouse scrolling has been disabled for Number Text-boxes, users will need to move the cursor outside of the Number Text-box in order to scroll through the field options area.

Impacted Areas
Mouse scrolling on Field Options

Tested Areas
Mouse scrolling on Field Options

---