Page and Data Source Constructs

This section describes a number of typical design patterns on how to construct pages that exceed the default functionality of the generated web pages. There are so many imaginable object combinations and settings that you may need guidance on how to construct popular functionality such as master-detail forms.

You will explore how many data sources you need on a page, how to interrelate data on one or more pages managed by different data sources, how to implement page navigation, and when to include pages in other pages.

To understand how the various constructs are put together, it is helpful to have knowledge of the concept of page stacking. This subject is dealt with at the end of the section.

Pattern	Title	Description	Type of Construct
1	Search-and-results on single page.	Search block for search conditions. The Results block is populated on Search button click.	Stand-alone page.
2	Master-detail form on single page.	Results page showing all parents and children on one page. An automatic query is executed on page-open.	Stand-alone page.
3	Search-and-results across two pages.	Search block for search conditions on page 1, results shown on page 2. Page navigation on Search button click.	Shared data source.
4	Master-detail across two pages.	Search and results blocks on page 1, more Results (child records) on page 2.	Page stacking, separate pages.
5	Re-used Search facility	Search facility for parent table inserted into a page that shows parent-child results.	Page stacking, embedded pages.
6	Classic foreign key lookup page	Lookup button for foreign key, user selects value from lookup page and returns.	Page stacking, separate pages.
7	Classic foreign key dropdown list	Dropdown list for foreign key	Stand-alone page.
8	Classic joined column	In addition to foreign key field, a name field from the parent table is shown.	Stand-alone page.