Loading
Feature degradation | Gmail Email delivery failureRead More
Visual Studio Code Based Modeler for Consumer Goods Cloud
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            pagePattern

            You are here:

            1. Salesforce Help
            2. Docs
            3. Visual Studio Code Based Modeler

            pagePattern

            The value of the pagePattern attribute determines which section types and how many you can use within a page.

            Required Editions

            Available in: Enterprise, Performance, and Unlimited Editions

            A page contains a PageHeader element and one or more sections depending on the pagePattern attribute.

            pagePattern Description Allowed Sections
            SingleSectionPage This page pattern describes a situation where a single section fills the entire page. This section is named masterSection. This indirectly states that the whole page is visible on all devices and isn’t split across multiple device screens. No additional logic is contained in this pattern. masterSection
            SingleSectionDialogPage This page pattern is similar to the single section page pattern, but the page is displayed in a pop-up dialog instead. masterSection
            MasterDetailSectionPage

            This page pattern is used when data in one section influences data in another section. The page using this pattern has the following sections:

            • masterSection
            • detailSection

            This page pattern also includes two data sources that must be linked to data in the process context. Whenever the data in the master data source changes, a special event is triggered to notify the detail data source of the change.

            A typical use case for this page pattern is a list view that contains overview data and a detail section that contains detailed information about the selected item.

            		 PageHeader, masterSection, and detailSection
            MultiSectionPage This page pattern consists of two horizontal sections that have no dependencies between them, which is dissimilar to the master detail section page pattern. This page pattern makes it possible to dynamically display a second section with an area whose area pattern is MultiArea. An example of this page pattern in the core app is in the Call::AgendaWeeklyView UI contract. There, the CallCalendar UI control is initially displayed in full screen mode. If the user selects a relevant menu item, the second section becomes visible and is displayed next to the call calendar. masterSection and planningSection
            SplitScreenPage

            This page pattern makes it possible to model a two-section page for a phone form factor. The user can switch between displaying the leftSection, for example, a list, and the rightSection, for example, a map. Unlike the master detail section page pattern, the two sections aren’t dependent.

            The SplitScreenButtons element as a child of the page pattern enables a mobile device user to switch between the two sections. It contains two buttons, each of which can have its own label and icon. No events are to be handled for the button; the switching is handled by the framework.

            A typical use case for this pattern is on a mobile device form factor, where it isn’t always possible to display two sections side by side. For example, it isn’t possible to display a list of calls (the Call Calendar daily view) and the map simultaneously.

            		leftSection and rightSection
            • onBackDiscardV2 Attribute
              Use the onBackDiscardV2 attribute to exit a setup flow without validation or saving. When onBackDiscardV2 is set to true, pressing the back button ends the current process without saving data or user changes, closes the flow UI, and reverts to the previous process without returning any values.
            • showNavigation Attribute
              The showNavigation attribute is supported in these page patterns (within the UI contracts):
             
            Loading
            Salesforce Help | Article