Inbox/Update Tests

From the TQM card in the home screen, there is a link to the inbox.

Update Tests Flow

  • Tests are created through the cronjob scheduler at the backend.

  • These tests created have a two-step workflow: Scheduled (initial state) -> Select Lab -> Pending Results -> Submitted (final state).

  • By default, tests which are in the workflow, will show up in the inbox of a plant operator. The inbox shows a list of cards corresponding to each test.

  • Each card contains data relevant to the test such as Test ID, Treatment Process, Stage, Output, Status, etc.

  • There is a dynamic action button in each card. According to the current workflow status, it will show either update status (scheduled state) or update results.

  • Clicking on the update status opens an update test screen which shows data about the test and a dropdown which has a list of labs configured in MDMS. A user can select one of the labs and update the test.

  • Clicking on update results opens an update test screen, which also shows the same test details, but the bottom card shows a list of benchmarks to be tested in that test. A user can enter these benchmarks and update the test. There is an option to upload a document as well, and at least one benchmark is mandatory to enter.

  • A success/failure toast is shown once the test is updated.

  • Filter and sort options are available in the inbox.

  • A user can filter by -> Treatment Process, Output Type, Date Range, Workflow Status.

  • A user can sort by date (latest first/latest last).

Plant Operator Inbox

API Details for Update Tests :

  • Use the pqm-service.

  • URL for inbox "/pqm-service/v1/_update".

  • Sample request object:

  • Sample curl for update:

Role-Action Mapping:

Role-action mapping is done for the "/pqm-service/v1/_update" endpoint for a plant operator user role, that is:

Update Tests (Select Lab)
Update Test(Add test result)

API Details for Inbox:

  • Use the inbox-v2 API.

  • URL for inbox "/inbox/v2/_search".

  • Sample request object:

  • Sample curl for inbox:

Role-Action Mapping:

Role action mapping is done for the "/inbox/v2/_search" endpoint for a plant operator user role, that is:

Was this helpful?