Issues Fixed in Field Management 2022 R5
The following issues were fixed in the Field Management R5 release.
To view customer suggestions and enhancements for this release, see the āWhat's Newā page.
General
Issues Fixed | Issue # |
---|---|
The portal update to version 22.4 failed for customers who attempted to update from versions prior to 22.2. The following error message was generated: Invalid column name 'DateCreated'. | 107790 and 108001 Note: Resolved in an update after release 22.4+. |
Windows Authentication failed for users if the Active Directory domain had more than 1,000 user objects. | 107045 |
Portal setting fields that allow rich text formatting are now limited to 20,000 characters. Previously, in rare cases in which customers had rich text entries beyond this limit, the web portal failed to launch and generated the following error message: Error during serialization or deserialization using the JSON JavaScriptSerializer. The length of the string exceeds the value set on the maxJsonLength property. | 107664 |
Portal settings that have a password or an encrypted key now have a Clear button that you can use to clear an existing value from that setting. | 108002 |
Field Management Mobile App
Issues Fixed | Issue # |
---|---|
Resolved production processing error when submitting mobile timecards with large crews. | 107864 |
Resolved issue with SMS invites for Field Management Mobile. This issue generated the following error message in the Mail Log: Recipient must be specified. | 107373 |
For employees who had signed off on timecard hours, the Signed Off status was not displaying above the employee's name on the timecard page in the mobile app. | 108010 |
Field Tickets
Issues Fixed | Issue # |
---|---|
The following error message displayed when attempting to bulk add users to the Payroll section of a Field Ticket and then changing the PR Group before saving: An error occurred when attempting to save the timecard. | 108000 |
Job Approval
Issues Fixed | Issue # |
---|---|
A loading error occurred when attempting to access the Job Time Approval page. | 107852 Note: Resolved in an update after release 22.4+. |
The Pay Period Ending drop-down displayed all PRCos and PRGroups, not restricted based on the user's access. | 107856 |
The pay period drop down is now limited to PRCo's and PRGroups that have job approval enabled in Grid Timecard Settings. | 107856 |
On the initial load of the page, the Job Approval grid was not filtering to the default status of Unapproved. | 108008 |
When viewing a closed pay period, the Approval Status is now read-only and defaults the drop-down to All. | 108007 |
Crew Timecards
Issues Fixed | Issue # |
---|---|
Multiple PRCos were displayed on the Timecard Dashboard. | 108013 Note: Resolved in an update after release 22.4+. |
Users in portal
setting User Group
To Restrict Line Edit / Add / Delete (Submit Only) on Grid
Timecard did not have the option to submit a
timecard in the Grid Timecard Actions drop-down. Setting location: . |
107775 Note: Resolved in an update after release 22.4+. |
When portal setting
Filter
Existing Grid Timecard lines based on Logged In User's Job
Data Security was enabled, non-Job Grid Timecard
Lines could not be saved to non-Shared Grid Timecard Templates.
Setting location: . |
107851 Note: Resolved in an update after release 22.4+. |
When a UD field in the Values column was edited and saved, amounts were changed to zero. | 107648 |
When a Closed Pay Period was selected, the Timecard Dashboard excluded Timecards that were not submitted. | 107913 |
In Timecard Approval, the Review & Approve All button now displays if there is at least one timecard line to be approved. | 108014 |