Complex Forms

Code can get really ugly real fast if the architecture design can’t support lot of scenarios. This is especially true with businesses that need to support multiple scenarios based on Country, State, Language, Business lines supported, Acquiring new companies, etc. For example if we have 50 states to support, that equals 50 variations. If you add 3 more business lines to support, now we are talking about 150 variations. If we support 2 different languages, equations jump to 300. This is crucial to businesses trying to expand in the future. Architecting software so that each one of these scenarios should have absolutely 0 impact on the next scenario. Versioning plays a crucial part in developing systems that are complex and will give us the flexibility to rollback a specific state or business line. We wrapped our complex form that in fact had exactly 300 different variations that we discussed above.

At BundleN, we experiment with stack combinations on our own time. For potential clients interested in this stack, we can always give a demo of what we have up until that point of time. You can reach us at

For more details on this stack, click here

Here is the latest about our Angular + Java project.


Complex Form

Task Details

Complex Form that needs to be dynamic and need to be state, company, business line specific in nature and should also support versioning.


Develop Patient Info Page

Task Details

Develop Patient Info Page. This page should have basic Patient info fields.

Form should vary by state, company, business line, version, etc.