Please find details below of the items included in this latest release.
Enhancements (3):
Warning Prompt Added for Unsaved Form Changes
When closing the Forms dialog using the X button, users will now receive a warning message. This prompt informs them that exiting without saving will result in the loss of any changes made. Users can then choose to continue with closing or opt to save their progress, ensuring data integrity and preventing accidental data loss.
New Connectivity Status Indicator for Mobile App
To improve visibility into connection issues, a new connection status indicator has been introduced in the mobile app. A green dot will appear in the app menu when the device is recently connected, and a red dot will indicate disconnection. Additionally, a red icon will be shown across all screens when the device is offline, helping engineers stay aware of their connectivity status at all times.
Note: This feature is controlled by a configuration setting. Let us know if youโd like this turned on for your engineers.
Signature Enforcement Added to Job Completion Flow
Improvements have been made to the process of capturing signatures within the job workflow. The Engineer Signature section is now marked as mandatory. If an engineer's signature is not provided a warning message is displayed and the equipment safe for use option is left unselected, the user will remain on the Engineer Signature page. This ensures proper completion of necessary information before proceeding to the next activity, enhancing data integrity and ensuring compliance during job execution.
Fixes (4):
Missing Forms When Raising Service Jobs with Linked Equipment Types
An issue was identified where appropriate forms were not displayed when raising a service job with an equipment type linked to a service type. This affected workflows such as raising a service task, adding a task to an existing job, and using the "Complete & Add New Task" option. The issue has now been resolved. The system correctly displays the relevant forms across all these scenarios, ensuring a consistent and complete job setup experience for engineer
Job List Visibility Issue After Issuing to Multiple Engineers
After issuing a job to multiple engineers, the job list did not refresh correctly for some users. In certain cases, such as for one engineer, the job list appeared blank until manually refreshed via the "In Progress" tab. This has now been resolved.
Job List Flicker on Multiple Devices
Resolved an issue where the job list on one device would flicker if the same job was sent to multiple devices. When an engineer began working on a job using one device while another displayed the job list, the second device would experience a flicker lasting up to 10 seconds, causing the job list to appear empty temporarily. This has been addressed by optimizing the process for updating job entries, ensuring uninterrupted workflow for engineers across all devices.
Fixed Blank Screen Issue on Pending and In Progress Tabs
Resolved an issue where the main job list screen might appear blank under certain conditions in the pending today tab. This occurred when there were no pending jobs, displaying a blank screen with a cancel icon in the top-right corner. Similarly, the filter tab also showed a blank screen with a cancel icon alongside filter and sorting options. After clicking the cancel icon, navigating to other screens such as Diary, Summary, or Scanner and then returning to the Jobs tab resulted in the screen remaining blank. The issue has been addressed to ensure the job list is displayed correctly after interacting with the cancel icon on the pending task or In Progress tabs.
Improved Task Ordering for Parent Equipment in Mobile App
An update was made to the mobile app to improve how tasks are ordered when parent and sub-equipment are involved. Parent equipment now appears first in the task list, making it easier to identify and manage related items. However, task numbers continue to be assigned based on service dates โ so if a sub-equipment has an earlier service date than its parent, it may still receive a lower task number. This change enhances usability without altering the underlying task sequencing logic.
โ
โ