Feature Requests

ntroduce a Purchase Order (PO) feature under the Financial Module and integrate it with the existing Procurement and Expenditures features to enable the complete procurement process to be managed within FacilityBot. Following the evaluation and recommendation of vendors through the Procurement module, users should be able to generate and issue a Purchase Order to the awarded vendor. The feature should support: Creation of a Purchase Order based on an awarded procurement. Use of each client's existing or customised PO template. Automatic population of relevant information from the Procurement process. Automatic population of key fields, such as: -- Date of issuance -- Awarded vendor -- Description of works or services -- Amount of work -- Completion date -- Other relevant procurement details Issuance of the PO to the awarded vendor directly from FacilityBot. Linking the PO back to the relevant Procurement and Expenditure records. Proposed Approval Workflow Explore the possibility of introducing approval workflows for different stages of the procurement process, including: (1) Approval before issuing the ITQ Procurement request is submitted for approval before the ITQ is sent to vendors. (2) Evaluation and recommendation Vendor submissions and evaluation results are recorded within FacilityBot. The recommended vendor is submitted for approval. (3) Approval before issuing the PO The Purchase Order requires approval before it can be issued to the awarded vendor. This would provide a complete audit trail of the procurement process, including the relevant submissions, evaluations, recommendations, approvals, and final PO issuance. [OMB]

Display the Fault Type and Request Description on separate lines for better readability. The Fault Type and Request Description are currently displayed together on the same line in the request list. This causes the information to appear truncated and difficult to read, especially when the description is longer. [ALR]

To have an Export button to the Accounts page that allows administrators to download the current list of user accounts in a standard file format (e.g., CSV or Excel).

Allow manager to customize the email content for Procurement-related emails: (1) Procurement invitation email sent to vendors. (2) Submission confirmation email sent after a vendor submits their quotation. Currently, the content of these emails is fixed and cannot be modified by administrators. [OMB]

To set a default priority for specific Location Tags. When a request is submitted for these Location Tag, the request priority should be automatically assigned (e.g., Low, Medium, High, or custom priority). This could ensures requests from critical locations are prioritized automatically. [NDC]

To allow managers to link vendors to parent checklists. This would better track vendor-specific servicing, inspections, and maintenance schedules using checklists, while providing clearer visibility of which vendor is responsible for each recurring task. [OJJ Foods]

To allow managers to be restricted by location tags, enabling them to view and manage only the contracts or licenses associated with their assigned locations. Currently, Custom Manager Roles in the Contracts and Licenses modules can only be restricted using labels. There is no option to restrict access based on location tags. [MWS] [CBRE NEA]

introduce a view-only permission for Custom Manager Roles, allowing managers to view contracts and licenses without the ability to create, edit, renew, or delete records. Currently, there is no option to grant managers view-only access to the Contracts and Licenses modules. Managers with access are also able to make edits. [MWS]

Giving the PIC more flexibility to access expenditure inside mobile apps. [OCS x MCM]

Having approval/Reject button inside Facilitybot website and Facilitybot Mobile Apps instead of have to go to external link in the email which give more smooth workflow and efficient work. [OCS x MCM]