Profit Ops Patch 2.1.12 has been released to the live environment. Changes and updates for the patch cycle ending 10-2-2024
Due to an issue with Dark Mode View, this article should be read using Light Mode.
Known Issues
Under certain rare conditions, printed work orders can show total gibberish when sent to the printer.
This is the result of an intermittent problem with the Adobe rendering engine and outside our ability to fix.
This can be worked around by refreshing the page and re-submitting your print.
Projects Module
Fixed an issue that could prevent work order gallon counts from updating after changes, or that could cause them to be blank.
Improved the mathematical logic for Total SqFt and TotalGallons calculations.
Improved number formatting for area details entry fields.
Improved validation checks for the area details entry fields.
Refactor of all other area details backend code.
Added data serialization checks for better database integrity.
Fixed an issue that could prevent the WO title from showing up on printed WO documents.
Work Orders
Fixed an issue that caused the Labor Tab’s Time Entry - Total Time fields not to be displayed, even though they were being correctly recorded in the database.
[NEW] Super and Foreman roles now have a dedicated version of the Labor Summary.
This aids in permission allocation and the display of relevant information for both roles.
Refactored the Reopen Workorder function to use woStore.$patch.
This change helps the system better organize the state of different active work orders and improves overall responsiveness.
This also introduces missing fields “Completed By” and “Completed At” in the API call, allowing us to ensure work orders are locked and unlocked correctly on bad internet connections.
Refactored the backend code for the Work Order Checkout View.
This improved readability and eliminated some small syntax issues that could have thrown errors in the future.
Fixed an issue that could prevent fleet delete buttons from appearing to users that have the correct permissions.
Added validation checks to prevent a fleet from being deleted or updated after it has materials logged on the material tab.
Added a forced rendering check for certain actions on the work order that will require the page to refresh after certain actions.
This helps ensure users are shown the most updated information.
Also helps prevent caching issues from showing the wrong information to users.
Fixed an issue where the various tab checkout buttons would not lock after the work order is closed, allowing users to continuously select the checkout button without seeing a response.
Fleet/Equipment Module
Removed fleet ID’s 31 and 46 from the valid fleet list.
Timecard Module
[NEW] Users can now edit existing entries from the TimeCard instead of only creating new ones.
Fixed an error that could occur when adding a MOB entry from the TimeCard that overlaps a previous one.
Fixed an issue that could occur when trying to select fleet for use on a MOB.
Fixed an issue where certain fields were not displayed or displayed incorrectly if the optional driver and flight information were not provided.
Corrected logic for the MOB entry to ensure both driver and flight must be zero to affect the flow.
Refined UI spacing and formatting.
Readability and formatting pass on all related program code.
Fixed an issue where information entered by the user on a previous “add entry“ could appear in the entry fields for the next one.
Fixed an issue with the date selector that prevented validation checks from running correctly.
Improved readability for the Punch Editor backend component.
This makes the code easier to troubleshoot and maintain without altering its functionality.
Fixed trailing comma in the Time Entry backend component.
This improves readability and prevents issues during JavaScript processing.
Improved the dynamic content UI for more flexible resizing.
This allows UI elements to adjust automatically to changes in screen or window size and resolution.
Improved error and edge case handling to accommodate rare situations where the “Total Hours“ field might not be available.
This allows the system to avoid throwing an error, and instead will indicate on the UI that information it was looking for is not available.