Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note: To simplify its setup, testing, and deploymentrunning, the creation of all report elements was done via a Java script (Source in SVN).

...

Note: To simplify its setup, testing, and deploymentrunning, the creation of all report elements was done via a Java script (Source in SVN ).

Best practices

Scripting

...

Setup of Reports

The Reporting module already provides a generic UI to define and to view reports. Even though this is good for an adhoc approach, to get familiar with the Reporting module in general and specific requirements for reports, this is also "click-intense". Besides this for now these reports are bound to a specific OpenMRS database installation (unless clever ways of myqldump and -load are used). If reports need to be

...

then it might make sense to externalize the creation of the various report elements. Besides the UI everything is accessible through the Java-API. With some Java knowledge, the creation of Cohort queries, Indicators and Report Definition can be scripted.

The "deployment" running of reports can be done in 2 two different ways:

  1. Through a module, which provides the Administration feature to set up (and remove) persisted report elements (good for production systems).
  2. Through a (misused) Junit testcase, which can easily be invoked from the local development environment (good for development and testing).

...