System Workflow

Different steps involved in the above diagrams are-

1. A new work order (WO) is created in FMP2 (either directly or through fmPilot).
2. The FMP2 hits the API endpoint and passes WO details to be updated in the database by the SP.
3. Service Provider (SP) chooses to view the WO list.
4. SP API sends the list of WOs to SP (fsElite).
5. SP chooses a WO and updates the status. The WO status is sent to the SP API endpoint that updates the new status in the database.
6. SP adds quotes for the WO.
7. The quotes added are sent to the API endpoint, which updates the database.
8. FMP2 user requests to see the quotes for providing subsequent approval.
9. FMP2 user approves the quotes and the approval flag is conveyed through API into the database.
10. SP (fsElite) requests to see the quotes decision.
11. fsElite makes a call to the API to see the quotes decision.
12. API provides the approved quotes information to SP (fsElite).
13. SP works on the WO (offline) and keeps updating comments, attachments etc.
    For e.g. A SP completes a WO due to which status of WO changes from In Progress to Pending SP Invoice.
    Once this change in status happens in fsElite, this needs to be synced up in client system using the set of APIs aligned with this task.
14. Each of the updates to the WO are sent to the API endpoint and API updates the FMP2 database.
15. Finally, when the work is completed, SP creates the invoice.
16. Invoice draft is provided by the fsElite to the API endpoint to be updated in the database.
17. Account and Payable/ team query the database for the WO invoice details.
18. Views the invoice info and updates status (approved/rejected).
19. SP attempts to see the status of the provided invoice on his WO.
20. fsElite queries the WO status for an invoice using the API call.
21. API fetches the WO invoice details from the database.
22. API provides the fetched WO invoice decision to the SP (fsElite).