# From Builder Technical Gaps & Solutions

**URL:** <https://talk.openmrs.org/t/from-builder-technical-gaps-solutions/25564>\
**Category:** Bahmni\
**Tags:** bahmni\
**Created:** [November 20, 2019, 10:52am UTC](https://talk.openmrs.org/t/from-builder-technical-gaps-solutions/25564 "2019-11-20T10:52:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![snehabagri](https://talk.openmrs.org/letter_avatar/snehabagri/32/5_5575768a8748004e209b776fc1b2916d.png) [@snehabagri](https://talk.openmrs.org/u/snehabagri)\
**Post date:** [November 20, 2019, 10:52am UTC](https://talk.openmrs.org/t/from-builder-technical-gaps-solutions/25564/1 "2019-11-20T10:52:17Z")

</div>

Please check the attached document for details:

[Tech solutions - Forms 2.0.pdf](https://talk.openmrs.org/uploads/short-url/s1qQK5tt4GwANPpC19vtdbgSqiO.pdf) (41.1 KB)

@angshuonline @binduak

---

<div class="post-metadata">

**Author:** ![snehabagri](https://talk.openmrs.org/letter_avatar/snehabagri/32/5_5575768a8748004e209b776fc1b2916d.png) [@snehabagri](https://talk.openmrs.org/u/snehabagri)\
**Post date:** [November 26, 2019, 9:27am UTC](https://talk.openmrs.org/t/from-builder-technical-gaps-solutions/25564/2 "2019-11-26T09:27:01Z")

</div>

**Related links:**

> [@\[Form2\] Form name change requires too many changes](https://talk.openmrs.org/t/form2-form-name-change-requires-too-many-changes/25642):
>
> 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](https://talk.openmrs.org/t/form2-concept-changes-do-not-reflect-on-existing-forms/25643):
>
> 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](https://talk.openmrs.org/t/form2-backup-of-json-files/25644):
>
> We do not create backup of form json structures, can we include it as a part of Bahmni backup command?

@angshuonline @bhiravabhatla