From Builder Technical Gaps & Solutions

[snehabagri]

Please check the attached document for details:

Tech solutions - Forms 2.0.pdf (41.1 KB)

@angshuonline @binduak

[snehabagri]

Related links:

[Form2] Form name change requires too many changes

Today when we want to make a change in the name of a form, we do not have any direct way from the UI. It leads to cloning the form with the same structure. Change in the form leads to following issues: 1.Requires change in Groovy 2.Will act like a complete new form (clone) and the old form will still be present, also causing issues while reporting. 3. Requires change in display control Suggested solution: Requires change in Groovy The form can pass to Groovy a list of operations to perfor…

[Form2] Concept changes do not reflect on existing forms

When we change an answer for a coded concept, it does not reflect in existing form, and requires us to create the next version of the form. Every-time a new version is published we also need to change groovy. Ideally we do not want a user intervention every time we add or remove an existing answer. In order to solve this, we want to propose a caching mechanism to store the concept answers and update the data on concept change event and forms read the data for answers from this cache.

[Form2] Backup of json files

We do not create backup of form json structures, can we include it as a part of Bahmni backup command?

@angshuonline @bhiravabhatla