...
There are three ways of connecting your form to your database. recommends that you understand read and understand each approach carefully before moving forward with form design in order to determine most efficient approach, and prevent the need to redesign later. This table can help you decide which design approach to use based on your business requirements.
The Doc URI Approach* | Post via Web Hook | The Business Rules Approach | Dynamic Options | |
---|---|---|---|---|
Overview | Automatically create the controls in your form based on your database table, and use the Document Action user interface to set up Doc URIs that can perform CRUD Operations. | Automatically post data from your form/workflow to your database mid-workflow using the Web Hook feature. | Write JavaScript business rules to perform CRUD operations. | Dynamically retrieve options at runtime from the Database Connector (or any RESTful web service) using the Options Src control property, no code needed. |
Recommended Use Cases |
|
|
|
|
Form Design |
|
|
| Use Checkbox, Dropdown, Radio or ComboBox control with the from palette design method. |
Performance | Call the DB Connector once for all operations (using the autocreate feature) → fast, reliable performance | Call the DB Connector once after the prior step unloads (Continue is clicked). | Call the DB Connector query for every add/update operation (this can impact performance) | Calls the DB connector for each instance of the selection control. Fast, reliable performance for non-repeating controls. Performance issues may be seen for repeating controls. |
Technical Skills | No code needed Create/Modify xsd schema document | No code needed Create/Modify xsd schema document | JavaScript code required | No code needed |
Documentation | Generating XML Schema | Data Sources | CRUD Operations Example | 10-Minute Doc URI Video | Post via Web Hook | Forms Designer | Palette Controls | Integrations | Business Rules HTTP Methods | Rule Examples | Control Property Settings - Dynamic Options |
...