feat: [DHIS2-9661][DHIS2-14830] first stage registration

[simonadomnisoru]

DHIS2-9661. The PR builds on work done previously in #3217.

Tech summary
Currently, the D2Form is rendered between the TOP and BOTTOM dataEntrySections definitions. I introduced the concept of placements.BEFORE_METADATA_BASED_SECTION to be able to render the stage dataEntrySections definitions in between the concatenated enrollment metadata and the stage metadata. The getCustomContent callback implements the logic to render the placements.BEFORE_METADATA_BASED_SECTION dataEntrySections based on beforeSectionId value.

• useBuildFirstStageRegistration retrieve the firstStageMetaData from IndexDB and computes the firstStage with access
• useMergeFormFoundationsIfApplicable when the useFirstStageDuringRegistration flag is active, the hook will create a new RenderFoundation which concatenates the enrollment and first program stage metadata. The concatenated formFoundation will be used by the EnrollmentWithFirstStageDataEntry and the program rules execution.
• useDataEntrySections defines the dataEntrySections of the EnrollmentWithFirstStageDataEntry form with the help of the new placements.BEFORE_METADATA_BASED_SECTION concept.
• EnrollmentWithFirstStageDataEntry.component.js is a DataEntry wrapper to build the form for the first program stage event.
• deriveFirstStageDuringRegistrationEvent prepares the event data in the format expected by the API.
• getStageWithOpenAfterEnrollment checks if the user should be redirected to /enrollmentEventNew or /enrollmentEventEdit after creating the TEI. The place where it is redirected depends if the event will be created or not. The event can be created either during first-stage registration or autogenerated.
• In RegistrationDataEntry.epics.js, the eventIndex is calculated and will be used when the user is redirected to /enrollmentEventEdit.
• Adapted the convertGeometryOut to be able to convert not only the foundation.featureType but also any customFeatureType like the stageGeometry
• Adapted the getApplicableRuleEffectsForTrackerProgram to accept a custom formFoundation and use it as the base for foundationForPostProcessing
• convertAndGroupBySection in RenderFoundation
  • loop the form values
  • grab the associated data element
  • convert the value
  • group it by the section group
• initMode - a new URL param used when navigating to the /enrollmentEventEdit page. When initMode is set up, this overrides any page logic on the initial load.

[eirikhaugstulen]

Hey @simonadomnisoru,
I've run into this issue where the required elements in the first stage is not treated the same ways of TEAs. The form treats them as valid after touch. See video below.

Skjermopptak.2023-06-20.kl.16.11.06.mov

[simonadomnisoru]

We should show the AOC selection if there are any program stages with «auto-generate event» or «show first stage on registration page» is selected for the program. We should use the same logic for the new and old dashboard.

This means that we should generate events for program stages with «auto-generate event» and «open data entry form after enrollment», even if we are using the new dashboard. The effect of «open data entry form after enrollment» will be that we navigate to the edit event page (not the new event page). We will have to add another url param to make this work I think (initMode=edit, this overrides any page logic on the initial load).

We should follow the logic described here for auto-generating the event: https://docs.google.com/document/d/1E5dBP5_BZZ0pLt573Xd0GQB6kve2WUpNdoew3kCFnUo/edit#bookmark=id.12acp8ay7jwz

Hey @JoakimSM, code updated. Can you take a look? Thanks!

[JoakimSM]

🎉 Nice, good work @simonadomnisoru.

[github-actions]

🚀 Deployed on https://deploy-preview-3267--dhis2-capture.netlify.app

[geethaalwan]

Tested successfully on 2.41,2.40.2,2.39.3,2.38.5 versions

[dhis2-bot]

🎉 This PR is included in version 100.41.0 🎉

The release is available on:

• AppHub release
• v100.41.0
• GitHub release

Your semantic-release bot 📦🚀