View Quick Reference

Prev Next

This topic is a quick reference when creating views to register within the framework using simple examples. Each view type can have greater complexity and may have alternative configurations.

  • Include the key in views, as a general rule. If a key is not included, add a control to a column in Construct Preview and mark it as a key.

  • Create columns for button/tabs/labels/toolbar controls.

  • The order of columns in the view will be the default order of columns on the page, but this can be changed by the ordinal property for the column in the page configuration.

  • Match prefixes and suffixes with your naming conventions set for the targeted WebApp.

  • Include the underlying page table and be descriptive when naming views.

  • Make views as simple as possible. It’s better to create several simple views and join them into a separate view.

View for a Grid

  • Default Naming Convention: web*Hor

  • Use for a Column and Row grid to show multiple records from a single view or table

  • Registered on Grid containers

View for a Property Card

  • Default Naming Convention: web*Ver

  • Use for a Property Card container

  • Shows a single record

  • Can be used to show key-bound detail data for a single record on a Grid using key based bindings for the Grid record and the record you want to display in the property card.

View for a List Box

  • Default Naming Convention: web*List

  • Used as the list source for list box and combo box

  • Select columns that are available on list boxes

  • Select a table or view that contains the desired columns and values

  • When configuring a column, the Key is the List Value and the Descriptor for the Key is the List Display

  • Do not use the underlying page table for the source

Refer to Add a List Box for more information.

Validation View

  • Default Naming Convention: web*Val

  • Used to run data validation rules against page data for any Event type, both page and row level, though most validations are row level and require a key

  • Validations can be run as a page event and do not require a key, but the event is run against the whole table or view. It is important to understand your page views in this scenario.

  • Select only the columns required to run the rule, or the columns helpful to the user on the notifications

  • If a key is not selected, the rule is applied at the page level and run against all records

Refer to Validation Rules for more information.