Discuss basic structure of generic custom form

[ifoche]

Just for the record, we finally chose to use the same engine that was used for Reactive Vaccination, being able to generate the custom form with an execution of that engine, instead of using a template that reads in execution time what needs to load. The idea is to make the custom form as performant as possible.

I keep this issue open for @tokland and @matiasgarcia91 to briefly describe the final architecture that is being implemented, for the future to use it as documentation

[matiasgarcia91]

The selected approach consists of a Node.js script with the following main dependencies:

• Typescript v3.1
• typed-html. Type safe HTML templates. It has support for JSX (.tsx files). Its modular structure is very similar to the way React components are declared.

The script receives as input:

• The data set ID to update.
• URL of the Dhis2 instance with username and password: http://{username}:{password}@{path}.

Example:

$ node lib/cli.js --url='https://admin:district@play.dhis2.org/2.30' --dataset-id='eZDhcZi6FLP'

The scripts retrieves the data set and its sections to build a custom form based on the mock-up provided:

• One tab per section.
• One row per data element.
• Two columns per category option combo.

Finally, the script sends a single POST to /metadata with a JSON containing both the new dataEntryForm as well as the updated dataSet referencing the new dataEntryForm.

The solution proposed for the Event capture forms of programs is totally analogous.