Page

The Page element defines the layout of the UI Contract. A page can cover multiple display screens, depending on the device type and device orientation.

• pagePattern
  The value of the pagePattern attribute determines which section types and how many you can use within a page.
• Bindings
  The Bindings element defines a container element that contains all the resource and binding data for UI controls.
• SplitScreenPage Pattern
  Use the SplitScreenPage pattern to divide the page into two sections, called LeftSection and RightSection.
• SingleSectionPage Pattern
  The SingleSectionPage pattern describes a page with only one section, called masterSection. The entire page is visible on all devices and doesn’t split to multiple device screens. Use the SingleSectionPage pattern to display a comprehensive overview of data from different sources, such as dashboard and cockpit on a single page.
• SingleSectionDialogPage Pattern
  Use the SingleSectionDialogPage pattern to display a section in a popup dialog. The SingleSectionDialogage pattern allows only one section, called the masterSection.
• MultiSectionPage Pattern
  The MultiSectionPage pattern consists of two vertical sections with no dependencies between them. It dynamically displays or hides a second section with a multi-area. The MultiSectionPage pattern requires one or more sections.
• MasterDetailSectionPage Pattern
  Use the MasterDetailSectionPage pattern when data in one section influences data in another section. The two data sources must be linked to other data in the process context. A typical use case is a list view that contains overview data and a detail section that contains information about the selected item.
• HeaderLine
  The HeaderLine element indicates a new control section. HeaderLine is optional, and you can use it only one time on a page. It can contain any number of image buttons and dropdowns.