Skip to content

Latest commit

 

History

History
111 lines (79 loc) · 3.88 KB

scenario_4.md

File metadata and controls

111 lines (79 loc) · 3.88 KB

Scenario: new application bio-exception (walkin)

Type: HappyPath

Persona required: MorocconMaleAdult, MorocconFemaleAdult

Registration user logs in via userid & password

Older packets will be deleted from local machine. This will be based on the parameter set in global param

Registration user selects new registration for application

Registration user adds demographic info of applicant

Registration user adds applicant's documents

Registration user adds applicant's biometrics:

  • face
  • leftEye
  • rightEye

Registration user captures applicant's photo as proof of exception

Registration user create a packet based on above info

Registration user approves registration, which means its ready to sync

Registration user synces the meta data of the packet like id, hash, etc

Registration user uploads the packet zip to the server

System logs in to mosip via Registration user's userid & password

System will fetch the status of registration with a total of 5 attempts and asserts for final status to be "PROCESSED"

System will fetch the UIN from server via registration id

Retains the data of active person and now it is save to switch person

System sets the 1th index person as active person (child)

for this case index 1 is child

System sets the 0th index person as active introducer (father)

Registration user selects new registration for application

Registration user adds demographic info of applicant

Registration user adds applicant's documents

Registration user adds all applicant's biometrics:

  • face

Registration user adds all introducer's biometrics:

  • face
  • leftEye
  • rightEye
  • leftThumb
  • rightThumb
  • leftIndex
  • leftMiddle
  • leftRing
  • leftLittle
  • rightIndex
  • rightMiddle
  • rightRing
  • rightLittle

Registration user create a packet based on above info

Registration user approves registration, which means its ready to sync

Registration user synces the meta data of the packet like id, hash, etc

Registration user uploads the packet zip to the server

System logs in to mosip via Registration user's userid & password

System will fetch the status of registration with a total of 5 attempts and asserts for final status to be "PROCESSED"

System will fetch the UIN from server via registration id