Feature Requests

The ability to give custom names to workflows for easier identification would be highly beneficial. Currently, all workflows appear very similar, which can make managing and distinguishing between them challenging—especially when there are many workflows created. Allowing users to give workflows unique, descriptive names would improve organization and usability.

The ability to filter requests based on the information included in the Notes section. Currently, managers can filter requests by searching for specific words or phrases within the request Description field but do not have the same capability for filtering notes. Adding this functionality would make it easier for managers to locate and manage requests with relevant notes. [Sentosa]

Currently the data doesn't include breakdown by fault sub types for service requests with fault types and sub fault types. [CPG]

Currently remarks are not needed when canceling PTWs

The addition of a Purpose/Description Tab allows users to clearly specify the intent and details of the work being performed, improving clarity and documentation. The "Export" Option enables efficient data extraction for reporting, tracking, and record-keeping purposes. These features enhance transparency and streamline workflows.

The ability to restrict manager access to Licenses and Contracts based on labels or categories. Currently, all managers can view licenses and contracts across various departments. Implementing label-based restrictions for custom managers would enhance privacy and streamline access control, ensuring managers only view data relevant to their department. [ALR]

The ability to auto-assign tasks to account tags rather than individual responders. This feature would streamline workflow management, as it would eliminate the need to edit workflows to add or remove specific responders. Assigning to account tags would provide flexibility in task allocation and simplify changes to team roles or responsibilities. [ALR]

The ability to link checklists to requests, requiring the responder to complete a checklist either before or after closing the request. [K+N]

The ability for responders to be prompted to perform (1) a pre-maintenance checklist when a request is assigned and (2) a post-maintenance checklist after closing the request. These checklists should be directly linked to the specific request type, and managers should have the option to configure these checklists according to their needs [K+N]

Currently, in the Mobile App, users can update parts quantity only after scanning the QR Code. Better if users can just select a part and then update the quantity (similar to Web)