[Uganda Project - Technoforte Team] NIN Generation at the time of Record Correction

[Naveen1401]

Summary

At the time of Birth Registration, if the parents' IDs are selected as NONE, in that case the application will go into the Awaiting ID workqueue, and from there the user has to request the REQUEST_CORRECTION and then provide the valid IDs. If the parent provides the NIN then it should go for the NIN generation.

Requirement

After approval of the correction, if the parent NINs are verified, it should proceed to the child NIN generations.

Current Behaviour

Currently, when we are correcting the record and providing the proper NIN for the parent, it is going for the NIN generation for the child, but the issue is in the MOSIP after NIN generation, it is making the Register request, because this functionality is present while we are registering the record for the first time.

return client.event.actions.register.accept.mutate({
    transactionId: `mosip-interop-${crypto.randomUUID()}`,
    eventId,
    actionId,
    registrationNumber,
    declaration: {
      "child.ninAvailable" : "YES",
      ...(isAlienId
      ? {
          "child.idType": "ALIEN_ID",
          "child.alienID": nationalId,
        }
      : {
          "child.idType": "NATIONAL_ID",
          "child.nid": nationalId,
        }),
    },
  });

Which is fine for the Registration flow, first we'll send the record for the 202, and after NIN generation, it will accept the register request.

But during the REQUEST_CORRECTION flow, instead of register.accept we need correction.approve, but the main issue which we are facing is, at the time of REQUEST_CORRECTION, we need to insert the generated NIN, and also we need to make the call for the correction.approve, so two flows are happening at a time, insertion of generated NIN and updating the corrected record.

Expected Result.

At the time of RECORD_CORRECTION, if the user updates the parent NINs it should update the parents NIN and also insert the generated child NIN.

[euanmillar]

@Naveen1401 I am looking into this and will get back to you as soon as possible.

[euanmillar]

@Naveen1401 I think you have to fork the mosip-api to achieve what you want. There is an SQLite DB. You could use that to store a custom flag and instead of calling register do a correction, but I am not sure if the JWT would support it. My opinion was that you shouldnt be registering these records in the first place. You should put them in a workqueue where printing is disabled in a REJECTED state. As per example commits here.