I have one implementation application with three different rulesets. It was built on a single framework. Each team is working on different ruleset and the entire application is part of a single implementation application.
Options which I have now:
1. Need to create a new HTML fragment and add it to all the portal harness rules, screen flow and work flow harness rules. If there is any new harness created, it should be added by default to the harness else it wont pick my JS rules.
2. The other option is to maintain three different fragments as shown below in the UserWorkForm. It is like creating nested fragments as shown below.
They was a confusion that the UserWorkForm should only be used for framework applications and cannot used for implementation layer. I don't see any problem with approach two as it is future proof as compared with approach 1 in the above case. If I use approach 1, I need to call the HTML fragment in every new harness of the application. Is there any alternative for this? Which would be the best approach in my scenario? Branching should solve this problem but the development will happen with individual rulesets and stack is getting updated at the later point of time.
Note:All the three teams are working in parallel on three different requiremnts of a single implementation in the individual rulesets. Any application can be moved to higher environments at any given time.