As an implementor I want to be able to create simple forms within OpenLMIS and inject them into business processes as needed so that OpenLMIS will collect a useful mixture of logistics and other types of data relevant to my use cases

to slot appropriately

Acceptance criteria (see examples below for more information)
Come up with a design for program data that at a minimum allows implementors to:

• Create forms, including labels, values (with basic data types: i.e. integer, decimal, short text, long text, date, etc.) and basic formatting of forms

• Injection of form data into business processes

• Hooks to allow data transfer between the program data service and other services

• Leverage existing xForms compliant tool if possible

• Design and document how this form data will be stored and made available to reporting (whether that's to Tableau or Jasper or ODK reporting tools--TBD)

Examples & Additional Context:
One example of form creation that needs to be supported by this feature is shown on regimens within the requisition process for ART (as shown here username='devadmin', password='Admin123'). Regimens numbers are not relevant to the requisitioning process per se, but are important additional data. Another example is the collection of cold chain equipment data in the distribution process. This is not logistics data either, but is easily accomplished while counting stock. You can see from the links that these may need to collect different data types (integer, radio box, boolean, string, etc.). Furthermore, the former is part of the requisition business process while the later is part of the distribution business process - so an implementor should be able to create a form and "inject" it into the appropriate business process based on their needs using this form creation tool. Lastly, the tool should support hooks for using the input data. In our first example, the number of patients on a regimen could cause the Calculated Order Quantity to update in the requisition process.