Here are the articles in this section:

This enables a user to manage stocks, besides facilitating stock reconciliation.

Using Stock Management

On this page, the following actions can be performed:

• After a successful login as a warehouse manager, a user lands on the home screen which consists of "Manage Stock", and "Stock Reconciliation".-

Manage Stocks

This screen consists of the following types of transactions that take place for the the inventory:

• Stock Receipt

• Stock Issued

• Stock Returned

• Stock Damaged

• Stock Loss

Stock Receipt

• When a user clicks on record stock receipt, the warehouse details screen will appear.

• The latitude/longitude captures the geo-location of the warehouse which can be fetched with the help of the location icon within the field.

• Clicking on the next button will navigate the user to the "Received Stock" details screen.

• The "Receipt Stock Details" form has some mandatory fields: product, received from warehouse, and quantity received.

• The optional fields include waybill number, quantity indicated on waybill, transport type, vehicle number, and comments.

• Clicking on the submit button will take the user to the success page.

Record Stock Issued

• This screen captures the mandatory fields: Product, Issued to warehouse, and the quantity.

• The optional fields include waybill number, quantity indicated on waybill, transport type, vehicle number and comments.

• Clicking on the submit button will go to the success page.

Returned Stock Details

This screen captures the mandatory fields: Product, returned to warehouse, and quantity returned.

The optional fields are waybill number, quantity indicated on waybill, transport type, vehicle number, and comments.

Clicking on the submit button will take the user to the success page.

Damaged Stock Details

• This screen captures the mandatory fields: Product, damaged during, received from, and quantity damaged.

• The optional fields include waybill number, quantity indicated on waybill, transport type, vehicle number, and comments.

• Clicking on the submit button will take he user to the success page.

Lost Stock Details

This screen captures the mandatory fields: Product, lost during, received from, and quantity lost.

The optional fields are wWaybill Number, quantity indicated on waybill, transport type, vehicle number, and comments.

Clicking on the submit button will take the user to the success page.

Stock Reconciliation

• When the user clicks on the stock reconciliation button on the home screen, he/she is navigated to this screen where he/she needs to verify whether the physical count and calculated stock values are the same or not.

• In the select product field, the user needs to select a product from the dropdown.

• There are warehouse name and administrative area fields as well, all of which are mandatory.

API details

File Path : https://github.com/egovernments/health-campaign-field-worker-app/tree/master/apps/health_campaign_field_worker_app/lib/pages/inventory

After a user logs into the HCM app, the project selection screen displays all the projects assigned to the user.

User actions

On this page, the following actions can be performed:

• A user has to select one project.

• After selecting a project, the system downloads the data for the selected project only.

• After every login action, the system will automatically syncs the data with the system.

• Since the user will log in only at the start of the day and before going into the field, there must be stable internet connectivity for the device to perform this process.

• A “Sync in Progress” window appears on the screen and the user cannot perform any other action until the process is complete.

API details

When the user opens the application, it asks them to first select the language. The selected language is highlighted in orange colour.

User actions

On this page, the following actions can be performed:

• A user can switch the language.

• A user can click on 'Continue' to navigate to the login screen.

File Path

Users are redirected to this screen once they select the preferred language in the previous screen.

User actions

On this page, the following actions can be performed:

• A user can log in to the app by giving the User ID and Password.

• The "Forgot Password" button gives a user the option to contact the administrator to reset if he/she has forgotten the password.

Users are redirected to this screen once they click on the "Forgot Password" button in the language selection screen.

User actions

On this page, the following actions can be performed:

• Clicking on the forgot password option in the login page opens a popup message “Please contact your administrator if you have forgotten your password”.

How the HCM App Interacts with the Attendance Package

Below is the diagram of the components that are there in the HCM App and attendance package, and how the interaction happens:

New files or changes needed in the HCM App:

1. Add attendance package dependency in pubspec.

2. Create a bloc that extends the attendance listener class and creates the override methods.

3. Create model classes that import attendance models and add companion class.

4. Create repositories local and remote as per project requirements and structure.

5. Add typedef for repositories in untils/typedef.

6. Initialise repo in network manager, and create oplog.

7. Create SQL tables in case of offline.

8. Add navigation to manage the attendance page from the HCM app, and pass the required fields.

Overview

This module helps in marking the attendance of the field users (referred to as attendees), who are supposed to work on the campaign till the campaign is live.

ROLE: DISTRICT_SUPERVISOR

User actions

This module has 3 associated screens:

1. Manage Attendance

2. Date and Session Selection

3. Mark Attendance

1. Manage Attendance

Once the supervisor clicks on the “Manage Attendance” button, the supervisor is taken to the attendance registers mapped to them. The attendance registers are to be created manually, by taking a combination of the project, and the supervisor or staff member is mapped to it.

.

Data Field to Manage Attendance Screen:

Attendance Completion Days Logic:

1. Fetch all attendance logs for the register.

2. Based on the sessions configured for the register, check for the logs where the entry time and the exit time are equal to the start and the end time of the session.

3. For individuals who do not have logs that are the same as the start and the end time will be by default marked as absent if any of the individuals' logs is present for the register.

//generateDateList will return the map of completed attendance Dates.

list = generateDateList(

e.attendanceRegister.startDate!,

e.attendanceRegister.endDate!,

registerCompletedLogs ?? [],

e.attendanceRegister.additionalDetails?["sessions"] != 2,

);

var completedDaysCount =

e.attendanceRegister.additionalDetails?["sessions"] == 2

? list.length ~/ 2 //for registers with 2 sessions

: list.length; ////for registers with single session

2. Date and Session Selection

The date selection range commences from the start date of the attendance register and extends to the end date of the register or today's date if today falls before the end date of the register.

• If the attendance for a past day is already submitted, then the CTA must change to view attendance from mark attendance.

Missed Attendance Logic:

Upon selecting the attendance register, a list of completed dates is generated. We iterate over the dates from the start date to the current date, checking for any missing dates in the list to identify missed attendance dates.

3. Mark Attendance

The trainees or supervisors should be able to mark the attendance daily twice (one for entry and exit) against each register (default configuration for sessions).

1. Supervisors can mark half-day, full-day, and absent - Definitions of the statuses are as follows:

   • Not marked: Default status in the register. This must be the status when the user has not taken any action on the line item.

   • Present: Tapping once must change the "Not Marked" status to 'Present' (Not Marked —> Present).

   • Absent: Tapping twice must change the 'Present' status to 'Absent' (Not Marked —> Present—->Absent).

   • Half-day (Only if config requires attendance once a day): Tapping thrice must change the absent status to half-day (Not Marked —> Present—->Absent—-> Half Day).

2. Save and Mark Later: If the user marks attendance for 10 out of 50 people, and clicks on save and mark later, the supervisor should be able to reopen the given attendance register while it is active and see the status of the attendance marked as per the last time they updated the screen.

3. Submit: If the user marks attendance for 10 out of 50 people, and clicks on submit, an error message is shown to mark attendance for all staff. After marking attendance for all staff, and clicking on submit, the supervisor navigates to the attendance recorded acknowledgement screen.

Marking attendance and sending to oplog logic implementation:

For the registers, for which attendance is submitted, we have a flag upload_to_server for each log. If this is true, then the attendance for the register is submitted.

As we cannot send absent logs to the server, we filter the present and half-day logs, and create the oplog for those.

For each marking, two log objects are created for sending to the server: ENTRY and EXIT as shown below:

[{

"registerId": registerId,

"individualId": attendeeList.individualId,

"time": entryTime,

"type": "ENTRY",

"status": "ACTIVE",

"tenantId": tenantId,

"documentIds": []

},

{

"registerId": registerId,

"individualId": attendeeList.individualId,

"time": exitTime,

"type": "EXIT",

"status": "ACTIVE",

"tenantId": tenantId,

"documentIds": []

}]

API Details