Learn more about our embedded OEM solutions for software vendors

Leveraging Subforms

One of the big benefits of using a no-code application platform like Qrvey is the ability to build components once, but use them in a variety of applications. Subforms are one such component that can not only save you a lot of time but also streamline your app building process.  With subforms, you can build a single master form that contains all of the fields you possibly need, then create various subforms, or views, of that form tailored for specific use cases.

Imagine a work order scenario where the initial request is submitted by a customer, assigned by a manager but completed by a technician.  You could create three separate forms for each of these operations, then link them all together, or you could just use subforms to keep all of the data in one place, and but still have separate views for each party.

Your customer would only need to see the fields that pertain to them, like the nature of the request and the urgency, while all of the other fields could be hidden from view.  Managers would then be able to view, but not edit, what the customer provided, and assign a date, time and technician to the problem.  Finally, the technician could complete their work, provide their notes and close the ticket.  

Creating subforms in Qrvey takes just a few clicks, and you can quickly choose which fields are editable, read-only or hidden, creating multiple versions of your web forms in no time.  Best of all, subforms can be used in multiple locations throughout your application, so components like user tables and logins can be reused anywhere you need.  

Previous
Next

Recent Posts

The Power of Data Profiling
The Pitfalls of WYSIWYG App Building
Bespoke Applications: How Qrvey Hits the Mark
Bespoke Application Building: What is it?
Leveraging Subforms
Subforms: The Game Changer
RAD & Shadow IT
Rapid Application Development: The Difference between Low-Code & No-Code
How to No-Code Your Way to Software Solution Success
Traditional low-code SaaS: How No-code Builders Bridge the Gap