📄️ Page and data source constructs
|Pattern|Title|Description|
📄️ Pattern 1: Single-record and multi-record areas
In this design pattern, some columns are displayed in a multi-record grid on the left, and other columns are displayed in a single-record side pane on the right. The side pane shows only information about the record that is currently selected in the grid.
📄️ Pattern 2: Search-and-results across two pages
In this design pattern, Search functionality is offered on a first page. Results are displayed on a second page.
📄️ Pattern 3: Create-and-confirm across two pages
In this design pattern, Create functionality (INSERT, the creation of a new data record) is placed on a first page, and Confirm functionality (the ability to either COMMIT or ROLLBACK the record just created) is offered on a second page. Ensure the data source's initial state is "New Record”.
📄️ Pattern 4: Master-detail form on a single page
In this design pattern, the Results area shows 2 data blocks instead of 1.
📄️ Pattern 5: Parent box and follow-on insert
In this design pattern, you make a travel booking in a page 1. Then you press a button to navigate to a follow-on page 2. This page 2 has two distinct purposes:
📄️ Pattern 6: Customised lookup query
This design pattern helps the user of a lookup window. It prevents the user from selecting lookup data that later turn out not to be allowed.
📄️ Pattern 7: Classic joined column
In this design pattern, you display information from a joined column. This information comes from (= is stored in) a parent table, and is displayed in a child table. You look up the information on the basis of the parent-child relationship, ie., by looking at the foreign key value(s) in the child table.
📄️ Pattern 8: Job called by web page
In this design pattern, a job (for a procedural SQL operation) is embedded in web page flow.