Feature Requests

Purchase Order Module and Procurement Workflow Integration
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]
2
·
New Feature
·
planned
[Checklists] Linking Summary Report / Cover Page
Users require the ability to link a Summary Report (configured as another checklist) that will act as a cover page and be linked to one or more completed child checklists. The Summary Report should be downloaded together with the linked/related checklist(s) as a single PDF report. Proposed Functionality A Summary Report checklist can be generated as an ad-hoc and linked to existing maintenance checklists. This checklist will function as: A summary report, and A cover page for the completed checklists. When the checklist(s) are exported or downloaded, the Summary Report should appear as the first page of the compiled PDF. [Scenarios] Scenario 1 – Single Checklist -> Each time a maintenance checklist is completed: A Summary Report is automatically generated and attached as a cover page. Both documents are exported together as one PDF report. Scenario 2 – Multiple Checklists -> In some cases, there may be multiple maintenance checklists completed for the same job. Users should be able to: Link multiple checklists with one Summary Report. Generate one consolidated PDF report containing: The Summary Report (cover page) All related maintenance checklists. The compiled report will be automatically submitted to the Finance Department or customer. Finance will use this combined report as supporting documentation for customer invoicing. Expected Outcome: The Summary Report and linked checklist(s) can be downloaded/exported as a single PDF document. The Summary Report appears as the first page (cover page), followed by the completed checklist(s). [Don Jon]
2
·
Checklists
·
planned
Load More