Users can view all the applications assigned to them in the employee inbox. And it provides multiple filters and search options to filter the applications.
OBPS Inbox uses InboxComposer React HOC to create the Inbox through various child components, for both mobile and Desktop Components.
The API used to fetch applications in the inbox
For viewing OBPS inbox these roles are necessary "BPA_FIELD_INSPECTOR", "BPA_NOC_VERIFIER", "BPA_APPROVER", "BPA_VERIFIER", "CEMP"
The MDMS links (blue text hyperlinks) are used while selecting the OBPS application type, service type, risk type with business service and status filters.
Refer to the config below for risk type definition:-
To provide the facility for the employee users to update the BPA application state.
The application details page is used to display the details of the application and also showcase all the actions that can be taken on the application.
The various step for the application:
In this step, the user can upload multiple documents and/or approve the already uploaded documents.
The user approves the uploaded NOC documents.
The user fills in the inspection details (date, time, question, remarks) and submits.
Here the user approves the required permit conditions and can also add new conditions.
All the screens are developed using the new-UI structure followed previously in FSM, PGR, PT, and TL. Certain new components have been introduced such as Multi-Document Upload, Approval Checks, etc.
Throughout the flow, some data is imported from the MDMS. Following is the list of MDMS data:
Checklist
RiskTypeComputation
Below is the MDMS config used to fetch MDMS data:
The localization module used across the OBPS module was rainmaker-bpa and rainmaker-common, out of which we initialized rainmaker-bpa with module initialization.
​All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
The search application feature provides a filter-based search tool to employees.
OBPS search application is used to search all the applications independent from the workflow/process instance data, which eliminates the presence of valid roles to search for an application from any business service.
Make use of the already documented applicationType and serviceType MDMS. Create a couple of hooks to coordinate and easily use the available filters.
