Bug Fixes 

Issue: Client is unable to see view history option for some records when they login with a particular admin role.
Tracking Code: TAPSUP-9932
Case Number: 2023-0912-7980939
Reported Version: 1.14.3.0
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

1. Login with the admin role.
2. Import the workflow.
3. Click the ‘View History’ option.

Expected Results of Steps
The "View History" option should be visible.

Actual Results of Steps
The client cannot see the "View History" option for certain records when logged in with the admin role.

Resolution
The issue where the client could not see the "View History" option for certain records when logged in with the admin role has been resolved. The "View History" option is now visible as expected.

Root Cause Analysis
The issue stems from consecutive submitWorkflow calls within the same session due to autosubmission occurring without delay. This process did not retrieve the latest details for the saved workflow. To address this, a change was done to obtain the latest result.

Impacted Areas
Submit workflow

Tested Areas

• Submit workflow with normal stages  
• Submit workflow with autosubmit with and without delay
• Submit workflow with esplitter stage

---

Issue: Client is unable to see all the stages in the completed stages list in the view history when they are using save before submitting stages.
Tracking Code: TAPSUP-9144
Case Number: 2024-0117-8115356
Reported Version: TAP 1.15.9.1
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

1. Import and preview the workflow.
2. Submit the workflow until the Legal Approval stage.
3. Save and submit to the More Information stage.
4. Follow the loop by submitting between the More Information and Legal Review stages.
5. In the completed stages under view history, only the More Information stage is visible.

Expected Results of Steps
We should be able to view all the stages that the record goes through.

Actual Results of Steps
In the completed stages under view history, only the More Information stage is visible, while the Legal Approval stage is not displayed.

Resolution
The issue where only the "More Information" stage was visible in completed stages, while the "Legal Approval" stage was missing, has been resolved. All stages the record goes through are now visible in "View History."

Root Cause Analysis
The completed stages view was configured to exclude stage updates, resulting in a partial display of stages. The resolution involved removing some of the logic to ensure all stage updates are now displayed correctly.

Impacted Areas
Stage update and submit

Tested Areas

• Stage update and submit
• Simple workflow submit
• Workflow w/collaboration stage
• Parallel workflow

---

Issue: When we tag form result value to the notifications and if we leave those fields blank then the title of the field is still shown in the email notifications.
Tracking Code: TAPSUP-9284
Case Number: 2023-0928-8002345
Reported Version: TAP 1.15.7.0
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

1. Log into TAP.
2. Create a workflow with two text fields and assign a 'Form result value' for both fields in the Notifications/Document/Document field, without selecting the "Exclude form field title" option.
3. Preview the workflow, leave both fields blank, and submit the workflow.
4. In the email notification, observe that the field titles still appear, even though no values were entered for the fields.

Expected Results of Steps
When form result values are tagged in notifications, and the corresponding fields are left blank, the field titles should not appear in the email notifications.

Actual Results of Steps
When form result values are tagged in notifications, leaving the fields blank still results in the field titles being displayed in the email notifications.

Resolution
The issue where field titles were displayed in email notifications even when the corresponding form result values were left blank has been resolved. Now, when form result values are tagged in notifications and left blank, the field titles will no longer appear in the email notifications, ensuring cleaner and more accurate communication.

Root Cause Analysis
An additional validation on cases with the "Exclude form field title" checkbox was added to ensure the processed value is consistent.

Impacted Areas
Email Notifications

Tested Areas

• Workflow Notification Level (SuperAdmin)
• Stage Notification Level (SuperAdmin)

---

Issue: Unable to edit the request and getting an error as "Error processing request".
Tracking Code: TAPSUP-9525
Case Number: 2024-0711-8300368
Reported Version: TAP 1.17.7
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

1. Log in to TAP.
2. Search for the required records.
3. Select "Edit request" – an "Error processing request" message appears.

Expected Results of Steps
When the user clicks "Edit request," they should be able to make changes to the request and then submit it.

Actual Results of Steps
User cannot edit the request due to an "Error processing request" message.

Resolution
The issue where users could not edit the request and received an "Error processing request" message has been resolved. Users can now click "Edit request," make changes to the request and submit it successfully.

Root Cause Analysis
Some collab users in the staging environment have Manager Workflow Permissions. If one of these collab users is deleted, it causes issues for the remaining collab users with Manager roles, preventing them from accessing or editing active records.

Impacted Areas
Workflow template permissions

Tested Areas

• Workflow template permissions for a Manager role
• Workflow template permissions for a Manager role in Collab Stage
• Super Admin, User, Non-Registered User, and Group Roles

---

Issue: Error in the stage reporting.
Tracking Code: TAPSUP-9644
Case Number: 2024-0802-8323615
Reported Version: TAP 1.17.10
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

1. Log in to TAP.
2. Create or import the workflow.
3. Access the Sisense report and review the time spent on each stage of the TAP request.
4. Compare the reported time with the time displayed on the TAP dashboard. The times for each request may not align or be accurate according to the dashboard.

Expected Results of Steps
The time spent on each stage should be consistent.

Actual Results of Steps
The time spent on each stage is inaccurate and does not match.

Resolution
The issue where the time spent on each stage was inaccurate and did not match has been resolved, and now the time spent on each stage is consistent and accurate.

Known Issue
TimeSpentStatus and TimeSpentOnStatus Data Missing in Analytics for "Stage Update" Relationship. 

If a relationship is named "Stage Update", the TimeSpentStatus and TimeSpentOnStatus data does not appear in analytics. This occurs specifically when the relationship uses the name "Stage Update", leading to the analytics not displaying these values.

Root Cause Analysis
The issue occurred because the TimeSpentOnStatus calculation included the StageUpdate/Save time, which should have been excluded. The "N/A" value displayed in the Sisense dashboard under the TimeSpentStatus column was a result of summing the StageUpdate/Save time, which led to confusion.

Impacted Areas
TimeSpentOnStatus calculation

Tested Areas

TimeSpentOnStatus calculation across all submission types, including its time calculations displayed on the Sisense dashboard and in the database.

---

Issue: Data being transferred from a previous request to a new one from a pre-population field in the audit trial.
Tracking Code: TAPSUP-9773
Case Number: 2024-0823-8347017
Reported Version: TAP 1.15.13
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce 

1. Create or import the workflow.
2. Preview the workflow.
3. Select the role responsible for approving the request.
4. Enter the email IDs for the selected roles.
5. Choose the number of users to add, select all the names, and save the workflow.
6. Go to the audit trail and verify the entered details.

Expected Results of Steps
When viewing the audit trail of the second request, only one email should appear, as it was entered in the form.

Actual Results of Steps
The audit trail of the new request displays all emails from the previous request.

Resolution
The issue where the audit trail of a new request incorrectly displays all emails from the previous request has been resolved. Now, when viewing the audit trail of the second request, only the email entered specifically for that request is shown, as expected.

Root Cause Analysis
The issue arose due to a flaw in one of the logics of FormMapping for handling onsubmit prepopulation rules. Some duplicate entries were eliminated to ensure that only the latest prepopulation rules are applied, so the fields reflect the most current values.

Impacted Areas
Workflow Stage Submission

Tested Areas
For workflow stage submission:

• On-submit Prepopulation (using user or grid data source for prepopulation)
• On-submit Prepopulation with Form Mapping (using user or grid data source for prepopulation)
• Simple Prepopulation with Form Mapping (using user or grid data source for prepopulation)

---

Issue: The completed details are not reflecting in the audit history.
Tracking Code: TAPSUP-9957
Case Number: 2024-0822-8345446
Reported Version: TAP 1.18.1
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

1. Create a workflow that includes loops.
2. Submit the workflow for processing.
3. After the workflow status is marked as completed, check the completed stages in the audit trail.

Expected Results of Steps
The completion details should be reflected in the audit trail.

Actual Results of Steps
The completion details are not appearing in the audit trail.

Resolution
The issue where the completion details are not appearing in the audit trail has been resolved, and it now functions correctly.

Root Cause Analysis
The discrepancy between the audit trail and the completed stages view was due to differing logic in each component. The resolution involved removing the restrictive logic to ensure all stage updates are now displayed correctly.

Impacted Areas
Stage update and submit

Tested Areas

• Stage update and submit
• Simple workflow submit
• Workflow w/collaboration stage
• Parallel workflow

---

Issue: Revision Overwrite function error with "Null insert to FBROW.filter".
Tracking Code: TAPSUP-9965
Case Number: 2024-0930-8387417
Reported Version: TAP 1.18.1
Workaround
None

Pre-Requisites
Access to TAP

Steps to Reproduce

1. Create a workflow.
2. Edit the workflow. 
3. Publish the updated workflow and save changes. 

Expected Results of Steps
The revision should be updated to "Normal."

Actual Results of Steps
When attempting to overwrite a workflow using the revision function, an error occurs due to a null value being inserted into a table/column.

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
The current "Import Revision" process/logic was updated to handle unset/NULL values correctly.

Impacted Areas

• Importing revisions for workflows with or without "Record Form" fields.
• Saving workflows

Tested Areas

• Importing revisions for workflows with or without "Record Form" fields.
• Saving workflows.

   

---