Eysal

Overview

Eyssaal portal allows communication between clients and vendors by associating clients' purchase orders with vendors' invoices. The portal behaves as a central system where vendors register to be able to submit their invoices to the already registered clients, and clients register so vendors can have access to them. So in theory the portal should attract both clients and vendors.

When a client is associated with a vendor, the vendor's admin can have access to all the POs. However, vendor's users can have access to only a subset of those POs.

Invoices are submitted and associated to POs. After submission, their status is set to payed, rejected, or any other status depending on the client's system.

Eyssaal portal should be able to communicate with MTBQ to use operators to OCR vendors' purchase orders.

Running development environment

• Run docker-compose up -d from /mtbq/eysal to run the eysal server, client and all dependencies
• You can access the web client at localhost:3000
• There are 4 different users that are used for development:

  • User: user.vendor@rihal.om
    Password: vendor
    Role: vendor-user
    

  • User: admin.vendor@rihal.om
    Password: vendor
    Role: vendor-admin
    

  • User: user.client@rihal.om
    Password: client
    Role: client-user
    

  • User: admin.client@rihal.om
    Password: client
    Role: client-admin
    

API

Click here to access server's endpoints documentaion.

TODO: generate the docs instead of creating them manually.