Versions Compared

Version Old Version 14 New Version Current
Changes made by

Pragya

Pragya

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

User Guide

This user guide is designed to provide assistance to Operators and Supervisors in successfully installing, running, and registering applicants to obtain their Unique Identification Numbers (UIN) on tablet devices.

...

If one or both of the Irises are not detected or encounter issues that prevent successful capture, the Operator has the option to mark an exception. To do so, the Operator must identify the specific Iris that is problematic and indicate the type of exception- either Temporary or Permanent. Additionally, the Operator may provide any relevant comments.

...

  1. After all the biometric data has been properly captured or any exceptions have been noted, the Continue button will be activated. The Operator can then proceed by clicking on the Continue button, which will redirect them to the Preview page. The Preview page will display the following information:

  • Application ID

  • Timestamp of Registration

  • Demographic data collected

  • Documents submitted

  • Biometric data recorded

...

  1. On the Operator Authentication page, operators are required to input their credentials (username and password) that were used during the login process.

Upon successful verification of the credentialsOnce that is done successfully, the packet will be is uploaded to the server and the operator will be redirected to the Acknowledgment screen. This screen includes the following information:

  • Application ID

  • Timestamp of Registration

  • Demographic data captured

  • Documents uploaded

  • Biometric data captured

  • Print option

  • QR code for the Application ID

  • Option to initiate a new registration process.

...

Download Pre-Registration Data:

An operator can download the pre-registration data of a machine mapped center while being online and store it locally in the registration machine for offline use. Now, when the system is offline and the pre-registration data is already downloaded, the operator can enter the pre-registration ID to auto-populate the registration form. Provided the machine is online, any pre-registration application can be downloaded irrespective of the center booked by the resident.

This pre-registration data is downloaded from pre-registration API as an encrypted packet and stored in the local storage. There is a batch job running in background for deleting the pre-registration packets after configurable number of days.

Note- Date Range of pre-registration data to be downloaded and storage location of pre-registration data in the registration machine is configurable. Also, this is synced as a part of configuration sync.

...

Upon receipt

Supervisor’s Approval:

Upon successful verification of the credentials, acknowledgement will be displayed, and the Application will be moved to “Supervisor’s Approval” section. This feature will only be available for the User who has Supervisor’s role assigned to him.

Once the packet is created by the Operator, as an additional check, Supervisor will have to go through each application to make sure the details filled are in coherence.

Step 1: The user goes to “Supervisor’s Approval” section from the Operational Tasks section. The user will be taken to the page where they can see the list of all the Applications created by the Operator. All of these Applications will be in “Pending” state.

Step 2: The Supervisor then clicks on the Application ID one by one. At this stage the Supervisor can either Approve the Application or he can Reject it. If the Supervisor decides to reject it, they also will have to mandatorily mention the reason of rejection.

Step 3: Once the Application has been Approved or Rejected, the Supervisor will have to authenticate himself by clicking on “Submit” button and thereby entering their Username and Password. The User can also bulk submit the Applications. The only pre-requisite is that the packet has to be in Approved or Rejected status (pending Applications cannot be submitted for uploading). Once they have successfully authenticated, the Application will be removed from the “Supervisor’s Approval” section and will be moved to “Manage Application” Section.

Step 4: Once the Application is either Approved or Rejected by the Supervisor and is submitted, those packets can be uploaded to the server from “Manage Application” section or can be exported to their local device storage.

Manual Application upload/export: Once the Application is either Approved or Rejected by the Supervisor, those packets can be uploaded to the server from “Manage Application” section.

Step 1: The user selects the packets that they want to upload (bulk upload can also be done). Once selected, the user will click on “Upload” button after which the packet syncs and get uploaded if there is internet connectivity.

In case of lack of internet connectivity, the User can also export the packet to their local device storage. They can also bulk export the packets by choosing the Applications and clicking on Export button.

On choosing to upload, the packet is uploaded to the Registration Processor. Once the packet has been successfully processed, a unique identification number (UIN) is generated.

...

In summary, the aforementioned steps can be followed by the user (Operator/ Supervisor) to register an individual by capturing demographic data, documents, and biometric data in order to generate their UIN.

...

New content added for 0.10.0 release

  1. Operator Onboarding: To begin the Onboarding process, the Operator is required to follow the steps outlined below. The operator, in order to log in to Android Registration Client, will have to onboard himself. This functionality will be available on first time online login only.

    1. On logging in for the first time, the Operator will be taken to the screen where they will have the following two options:

      1. Get onboarded: This flow is present for the system to verify Operator’s biometrics with their registered biometrics. This is to enable local deduplication.

      2. Skip to home: This flow is to dodge “Operator’s Onboarding”. If the user selects this, they will be taken to the “Homepage” after which the user can get started with Resident registration. One of the pre-requisites of this flow is to have “Default” role mapped to the center.

        1. image-20240612-100557.png

      3. Steps to Onboard Operator’s Biometrics:

        1. The user will be taken to the Biometrics Capture Homepage where he will be able to see all the below biometrics:

          1. Face capture

          2. Iris capture

          3. Left hand finger capture

          4. Right hand finger capture

          5. Thumb capture

          6. image-20240612-074118.png

        2. The user will then have to capture all the above listed biometrics one by one

        3. Steps to capture the biometrics is given above - put hyperlink here

        4. Once all the biometrics are duly captured, the below ackowledgement message will be displayed on the screen.

  2. Dashboard: The Operator can access the dashboard where he can view the following:

    1. Packets created: This will show the total number of packets created from the time Android Registration Client was installed.

    2. Packets Synced: This will show the total number of packets synced from the time Android Registration Client was installed.

    3. Packets Uploaded: This will show the total number of packets uploaded from the time Android Registration Client was installed.

    4. User details:

      1. User ID: This will show the list of User IDs of the Users mapped to the device.

      2. Username: This will show the list of Username of the Users mapped to the device.

      3. Status: This will show the status of Users mapped to the device. This can take values such as onboarded, active, inactive etc.

...

In summary, the aforementioned steps can be followed by the user (Operator/ Supervisor) to onboard themselves, update their biometrics or view the Dashboard.

Update UIN: In a scenario where the Resident wants to update their data, they can do so by letting the Operator know their UIN along with the data that needs to be updated. Residents can update their demographic details, documents and biometrics using this feature.

Step 1: Go to “Update UIN” from the Homepage

Step 2: Enter UIN of the Resident and choose the data to be updated.

Step 3: Enter the data that the Resident wants to update. It could demographic data, documents and biometrics.

Step 4: Once all the required data is filled, the User will be taken to the Preview screen (data can still be modified) and then to the Acknowledgment screen (data cannot be updated hereafter).

Step 5: The user will then have to authenticate himself using his Username and Password. Once the authentication is successful, the packet will be uploaded to the server.

  1. Logout: Using this feature, once the user is done with their registration and other activities, they can logout. If there are no background tasks running, the user will be immediately logged out. While if there are tasks (like sync) running in the background, the user will be notified about the same. From here if the User wants to cancel logout, the background activities will keep running where as if the user choses to logout, they will be logged out and the background activities will be terminated.

  2. Adding handles during New registration: When an Operator is registering a resident, while filling the demographic details section, one of the mandatory fields will be marked as “handle”. This mandatory field that is marked as handle has to be unique for each resident.

  3. Authentication using handles: Once the resident is registered and the handle attribute is duly entered, that attribute can be used by the resident to authenticate themself.

...

DESCOPED CONTENT: vibha gondkar : Please do not update the below content.

  1. Update Operator onboarding: The Operators can also update their biometrics. In this scenario, the Operator will have to capture all their biometrics. On doing this, the previous biometrics captured during Operator Onboarding will be overridden by the newly captured biometrics. Steps to update Operator’s Biometrics:

    1. From the Home page, go to “Operational Tasks”

      1. Screenshot_20240528-152836-20240528-100128.png

    2. Select “Update Operator Biometrics”

      1. image-20240528-101747.png

    3. The user will be taken to the Biometrics Capture Homepage where he will be able to see all the below biometrics:

      1. Face capture

      2. Iris capture

      3. Left hand finger capture

      4. Right hand finger capture

      5. Thumb capture

      6. image-20240612-074139.png

    4. The user will then have to capture all the above listed biometrics one by one

    5. Steps to capture the biometrics is given above - put hyperlink here

    6. Once all the biometrics are duly updated, the below ackowledgement message will be displayed on the screen.

      image-20240528-110409.pngImage Modified

Handles Feature Authentication:

Assumption: Handles feature is enabled. Email Id is marked as Handles during registration.

Scenarios: The resident is trying to log into Resident Portal using Handles (i.e. email Id)

Step #1: Open Resident Portal and go to “UIN Services.

...

Step #2: The resident will be taken to eSignet login page.

...

Step #3: Choose the option to “Login using OTP”

...

Step #4: Enter the attributes marked as Handle (email Id in this case) and click on “Get OTP”. OTP will be sent to registered email Id and/or mobile number

Step #5: Enter the OTP received over registered email Id and/or mobile number

Step #6: Select/ deselect the Claims based on preference and click on “Allow”.

...

Step #7: You have now successfully authenticated and logged into Resident Portal via eSignet using handles (email Id in this case)

...