Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 laterThis table can help you decide which design approach to use based on your business requirements.


ConsiderationsThe Doc URI Approach*The Business Rules ApproachDynamic 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.

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
  • Create or update multiple records at a time
  • Perform multiple CRUD operations in each database call
  • Create or update a single record
  • Get/Write only a few values from/to the DB
  • Populate options in a repeating selection control, and/or use a complex option label 
  • Standalone selection control (not repeating)
  • Simple value and label from a DB column
Form Design
  • from Schema design method
  • Instantly creates controls that match your DB columns' names and types
  • Some control properties available in form designer, others edited by modifying the schema
  • Automatically passes all control values in Doc Action
  • from Palette and/or from Schema design methods
  • Designer creates and configures all controls to match Database column names and types. 
  • All control properties available for editing in Form Designer (from Palette)
  • Must pass each individual control value in Business Rule(s)
Use Checkbox, Dropdown, Radio or ComboBox control from palette.
Performance

Call the DB Connector once for all operations (using the autocreate feature) → fast, reliable performance

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

JavaScript code requiredNo code needed
Documentation

Generating XML Schema | Data Sources | CRUD Operations Example | 10-Minute Doc URI Video

Forms Designer | Palette Controls | Integrations | Business Rules HTTP Methods | Rule Examples

Control Property Settings - Dynamic Options

...