fix: [DHIS2-17854] validate the assigned values from rules engine

[simonadomnisoru]

DHIS2-17854

Tech summary

• extracted the validateField logic from the FormBuilder.component into an external file.
• added a function, validateAssignEffects, that also calls validateField. The common function runs every time the rules engine finishes executing and before the assigned values are stored in Redux. To improve performance, only the last assigned value is validated, since it is the one stored in the redux formsValues key.
• switchMap, from() and of() were used in the epics to handle the async validation checks
• to prevent the user from clicking save/complete while an async validation is running:
  • In forms that rely on withSaveHandler.js, depending on the form logic, the actions startLoadDataEntry, startRunRulesPostUpdateField, and startRunRulesPostLoadDataEntry will be dispatched before running the validations. These actions will add an entry in dataEntriesInProgressList that will show the waitForPromisesDialogOpen modal if necessary.
  • In the WidgetProfile that does not rely on withSaveHandler.js, the Save button will be disabled

[github-actions]

🚀 Deployed on https://deploy-preview-3783.capture.netlify.dhis2.org

[JoakimSM]

I have made a few structural suggestions that I hope is reasonable. Open to discuss if you disagree of course.

I'm also wondering, since we are dealing with potential async validations here, what are we doing to prevent the user from clicking save/complete while an async validation is running? I couldn't see this being handled properly, but I very much might have missed something.

[JoakimSM]

If I'm not mistaken, we are validating all the form values in the formbuilder when opening the form, so it would probably be best to skip the assign validations here (and other places where we are opening forms)

[simonadomnisoru]

I skipped the assign validations when opening all the forms. Thanks for the feedback!

[JoakimSM]

I have made a few structural suggestions that I hope is reasonable. Open to discuss if you disagree of course.

I'm also wondering, since we are dealing with potential async validations here, what are we doing to prevent the user from > clicking save/complete while an async validation is running? I couldn't see this being handled properly, but I very much > might have missed something.

Hi @JoakimSM, I implemented the suggested structural changes. Regarding preventing the user from clicking save/complete while an async validation is running, in withSaveHandler.js there is already logic for this handled by the waitForPromisesDialogOpen modal. There were only a few forms where the actions to enable/disable the waitForPromisesDialogOpen modal were missing and I added them. For WdigetProfile, the only form that does not rely on withSaveHandler.js, I added logic to disable/enable the Save button.

Can you have a look? Thank you!

It does indeed seem like this is handled. Thanks.

[JoakimSM]

Nice 🎉 Looks good to me

[geethaalwan]

Tested successfully on 2.42,2.41.3,2.40.7,2.39.8 versions

[dhis2-bot]

🎉 This PR is included in version 101.19.1 🎉

The release is available on:

• AppHub release
• v101.19.1
• GitHub release

Your semantic-release bot 📦🚀