Feature Requests

Currently, due dates can only be configured relative to the request creation date/time. This may not be suitable for request types that are tied to a future event or scheduled activity. [CPF]

It would be useful to include a dedicated Requestor column in the Expenditures list view, displaying the requestor name or details. This would improve visibility, simplify review and approval processes, and reduce the need to open individual expenditure records to identify the submitter. [Mandai]

It would be useful to include the requestor's name and/or account details directly in the approval request email. This provides approvers with immediate context, improves transparency, and helps them make quicker approval decisions without needing to navigate into the request first. [Mandai]

Currently linked Asset only shows the its ID but not its Asset Type or/and description. It would be useful to have an option to display on this page and also on the QR code how the QR codes are generated for like Assets. This would make filtering/sorting or downloading QR codes easier [Travelbee]

Currently, when duplicating a checklist row that contains conditional logic, the duplicated row does not inherit the same logic configuration of original row. Users must manually recreate the conditional logic for each duplicated row. It would be useful for duplicated rows to automatically copy the existing conditional logic from the original row. This would significantly reduce setup time and manual configuration effort, especially for clients creating large checklists (e.g., 100+ rows) with similar logic conditions. [KWSH][OJJ Foods]

Currently, there is no convenient way to sort or filter survey submissions to quickly identify the most recent responses. It would be useful to include sorting and filtering options (e.g., by submission date, latest first, oldest first, status, or survey type) to help users efficiently review and manage survey submissions, especially when dealing with a large volume of responses. [Cargill]

Currently, assets displayed on the Map Dashboard appear visually similar, making it difficult to distinguish between different asset categories or operational boundaries (e.g., assets inside vs outside the highway boundary). It would be useful to provide ways to visually differentiate assets on the map, such as through: Different colors Icons/markers Labels Boundary overlays or zones This would improve visibility, monitoring, and operational decision-making, especially for clients managing assets across different regions, classifications, or maintenance responsibilities. [ALR]

Allow email reminders to be sent to Account Tags instead of individual email addresses. This makes it easier to manage recipient changes (e.g. new team members) without manually updating the email list each time. [MWS]

on iOS devices, the layout and usability can be challenging. The quantity input field, +/- controls, and keyboard placement are not mobile-friendly and may block visibility of important fields during stock updates. On Android - the +/- is not available on the keyboard [OJJ Foods]

Currently, chatbot conversations can be difficult to navigate once users are deep into a flow, and there is no easy way to restart or return to the main menu. Conversations also do not automatically reset after inactivity or completed interactions. Suggested improvements: Add a dedicated “Back” or “Return to Main Menu” button during chatbot flows Implement automatic chat/session reset after a configurable idle duration or completed interaction Add a visible “Start New Chat” or “Reset Conversation” button for users to easily restart the chatbot flow [OJJ Foods]