Release Summary

The TAP 1.22.X1 release includes bug fixes, internal defects, and known issues for a better user experience.

Bug Fixes 

Issue: The TAP Workday Integration failed to import user data into the TAP environments. The integration now successfully imports user data into the TAP environments.
Case Numbers: 2024-0809-8332166
Impacted Areas
TAP Workday Integration

Issue: A few fields were incorrectly visible during the Collaboration stage when a super admin used the Edit Request option on the Workflow Dashboard. The issue has been resolved, and the fields now display correctly based on the configured visibility conditions.
Case Numbers: 2024-1217-8460970
Impacted Areas
Edit Request

Issue: The "Save & Submit" buttons appeared early on the Intake stage, even when the form conditions to display them were not fully met. The buttons now remain hidden until all required conditions for the Intake stage are satisfied, ensuring they only show when appropriate.
Case Numbers: 2025-0107-8475416
Impacted Areas
Submit Button

Issue: The alternate language selection in the second half of the workflow was not applied correctly. Only the default language was displayed even when a different language was selected. The form now updates fully based on the selected language as expected.
Case Numbers: 2025-0314-8537811
Impacted Areas
Alternative Language Functionality

Internal Fixes

Issue: The size of the WorkflowStatus column in the FBResultSet table was increased from 700 to 1024 characters. In the Non-Super Admin stored procedure, the temporary table continued to define the column with a 700-character limit. The temporary table definition has now been updated to match the new column size of 1024 characters.
Impacted Areas
Non-Super Admin stored procedure (specifically the temporary table definition within it)

Issue: The Submit button was appearing at a stage when only one section remained after condition changes, even though it was supposed to be hidden based on conditional logic. The button now respects the defined conditions and no longer appears incorrectly.
Impacted Areas
Submit Button

Issue: After entering the Requester Name field, the Save & Submit buttons were appearing even though the conditions to display the Submit button were not met. The buttons now display only when the correct conditions are satisfied.
Impacted Areas
Save & Submit buttons

Known Issues 

1. Sometimes the Submit button shows up even when it should not, such as when a section is hidden using the Form Wizard. However, this does not affect the workflow functionality. 
2. The Submit button may appear even when it should not, especially if a field that controls its visibility is hidden. However, this does not affect the workflow functionality.