PSA 2022 R2.0.1 - Release Update
Below is a summary of the Resolved Issue addressed by this release.
This release also delivers Upland Analytics 2022R1.2, including these Resolved Issues.
Note: This page could be updated as new information becomes available.
Resolved issues (PSA)
1151943, 1155202, 1156897 | TE-87415 | When searching for Projects through the Global Search, the results now return the correct Projects when Users Project Scoping has been implemented. |
1150971 | TE-87388 | Fixed an issue whereupon the tool tip containing the list of Assigned Users was not properly displaying when the Timesheet was in a State having a name containing special characters. |
1151870 | TE-87374 | The Expense Report Process Date column within the Expense Manager now displays the date only when the Expense Report is posted in an Expense Payable Batch. |
1150948 | TE-87373 | Fixed an issue with the Work Plans wherein the Sort Order of the View was incorrect when EAC was not enabled. Note: If EAC is enabled for View, the sorting order is as follows: Booking Type > Name > Task name. |
1150373, 1151691, 1155126 | TE-87371 | Improved the User List performance for a scoped User, when trying to select a User to Impersonate. |
1150561,
1150659, 1158008 |
TE-87350, TE-87643 |
When picking an Assignment in my Timesheet, the auto-selection and filtering logic is now working as expected. |
1150227 | TE-87338 | Fixed an issue wherein an error was produced while loading the Assign Users page if some Users were not in logged User's Scope. |
1153119, 1155107, 1156206 | TE-87461 | Users having numeric values as their Logon name can now access Upland Analytics as expected. |
1149367 | TE-87343 | Fixed an issue wherein the Process PO Notification Automation Service was failing if a Client PO line item (Name) exceeded 100 characters in length. |
Resolved Issues (Upland Analytics)
N/A | TE-87401 | Fixed an issue with Upland Analytics, wherein under certain conditions, using a Date Filter was returning erroneous values. |
351244 , 346041 |
TE-55356 | Fixed an issue with Upland Analytics, whereupon using multiple Custom Fields in the same Formula resulted erroneous values. |