Create a page collection to accommodate tabbed content that can be used across
experiences.
Before you begin
Role required: admin
About this task
Use page collections to create tabbed content in your experiences with the Tabs
component in UI Builder.
Pages within a page collection don’t have access to the parent page's URL parameters
or data resources. You can set conditions for pages in a page collection to define
which page to display to certain audiences. Page templates are not supported inside
a page collection.
Procedure
Click Create > Page collection.
On the form, fill in the fields.
Table 1. Create a page collection
form
Field
Description
Name
Name to track your page collection internally.
Controller
Controller that defines the data for the page collection.
App shell UI
Type of app shell UI that you want to use with the page
collection. The app shell is the wrapper of the page contents, which
is similar to the functionality of a web page. The app shell can show
things like the logo of your company, user preferences, and the search
icon. For more information, see Define UI experiences using app shells.
Description
Short description to help find your page collection. Write a
description that helps page builders understand what content is
included in the page collection.
Application scope
Application scope defines which application that the page
collection is part of. To create a page collection in a different
application scope, change the application scope in the platform and
then create a page collection in UI Builder.
Click
Create.
Click Edit page
collection.
A new tab opens to the page collection editing
screen.
Click Start editing.
Click Create a page
Enter a unique name for the page in the Name field.
Specify a path for your page in the Path field. UI Builder generates a default path based on the name that
you provided in the previous step.
Note:
The application scope defaults to the scope that the user is in. For more
information about the application scope, see Learn about security and roles.
Click Create.
Optional: Set advanced settings such as required and optional parameters, as well as variant
settings.
Select Add required parameters to add any required
parameters to your page URL.
A required parameter is a piece of data that your page requires, such as a sys_id, table, or query. Required parameters are useful for components, because they can bind to the value of the required parameter. For more information, see Manage UI Builder pages and page variants.
Select Add optional parameters to add any optional
pieces of data that you want to add to the URL of your page.
Unlike required parameters, optional parameters are always name and value pairs that work regardless of the order they’re provided in. For more information, see Manage UI Builder pages and page variants.
Click the required or optional parameter in the URL, and in the
Test values field type a value, such as
incident.
You add a test value to your page to populate data into the page as a way to test it. For example, if you add a table as a required parameter, you could add a test value of incident to bring in test data on the
incident for that table. For more information on test values, see Test values in a page.
Select the Variant tab to set the audience and
conditions settings for your page.
When you create a page, UI Builder also creates a
variant of the page for you by default. A page variant is a variation of
your page at the same path that lets you target experiences for different
audiences using user criteria. For example, a page for managers, and a
variant of that page for the manager's direct reports. For more information
about creating a variant, see Create a page variant.
