Includes “Provider Encapsulated” Re-architecture of the entire Form Engine, Data-driven form Pre-fill, more powerful Reference fields and parent-child functionality,
Re-architecture
A milestone event, for a much more modern API-enabled architecture, separating the core app from its connection with QB and other platforms (“Providers”). It enables scaling to new platforms much quicker, easier and on a standardized basis, as well as enabling the Form Engine to be integrated inside other applications. Being API-enabled also allows us or partners to write plug-ins to extend the Form Engine’s functionality without getting into the source code...a big technical liberator.
Form Pre-filled Data
Pre-fills fields in an Add Record form with dynamic data or static data from existing Quickbase records. This single feature extends the Form Engine in powerful ways and more use cases. For instance, if you have 100 locations or 1,000 pieces of equipment, you can take one form and instantly make it 100 location-specific or 1,000 equipment-specific forms, and the end users don’t even need to know...the forms just know what location or piece of equipment they’re related to. This is particularly powerful using QR codes for mobile forms.
Reference Fields and improved Parent-Child Functionality
“Related Parent” fields can now be used in forms to let the user choose a parent record to the record(s) they’re creating on a form, and choose the parent with the QB record-picker fields and search functionality. When a parent is chosen, any Lookup fields on the form auto-populate, pre-filling the form with data from the selected parent.
So for parent-child functionality, a user can:
Create a parent and child record(s) on the same form and relate them.
Add a child record and choose or change the parent record (or related parent can be pre-filled in the form). Also choose multiple parents (from different tables) for the same child record.
Add child records to an existing parent record (and the parent record can also be editable).