Below are settings available on Custom Pages and the actions they
perform.
1. Page Title
Action: Edit the title of the page. This is displayed on the Admin View
and in the Custom Page list on the Manager View.
2. Visible & Active
Active: If toggled on, page is ready to view and be available
in the Custom Page list (if Visible is checked off), on the Home Page (if set
up), under Analyze, or used in drilldowns or in other custom pages.
Visible: If toggled
on, the page will show in the Custom Pages dropdown on the Manager view for the
roles who have access to the page. Can only be visible if the page is Active,
‘Base Object’ is not set, or ‘Base Object’ is set and ‘Use employee of user’ is
checked (see 4 and 6 below).
3. Use Layout
Action: Change the
layout of the page.
· Default – standard page, no sidebar
· With Sidebar – Default with a sidebar to
navigate based on the Base Object (Employee, Comp Cycle, Department, Fund, etc.)
· Tabbed – Default with tabs across the top to
organize data
· Default – Wide, With Sidebar – Wide, Tabbed –
Wide – as described above, but optimized for larger desktop screens
· Modal – used for Secondary pages only, won’t
be available in the Custom Pages list on the Manager view
4. Base Object
Action:Determines
what records the content added to the page should key off. Combination
of the selected sidebar option (Employee, Comp Cycle, Department, Fund, etc.) and
comp cycle drives what data is displayed on the page.
· Required for People page and any Sidebar pages
– There must be a unique link between the Base Object and any other objects
you’re referencing data from on the custom page.
5. Default Currency
Action: Choose
which currency the page values default to for all users. When not selected, the
currency values on the page will show in LOCAL and users have the option to
change the page currency in their view if their role has access to the currency
dropdown.
6. Use Employee of User
Action:For pages
with a base object of Employee Comp Cycle, set page context to the employee
associated with the logged in user. User will only see their own data for
fields their role has access to see. The User’s role also needs access to ‘see
their own record’ for this to work.
Can be used when the base object has
an employee of record (employee is a reference field on the object) and the
page layout has no sidebar.
7. Use on Analyze Page
Action: Page will
display on the Analyze tab on the Comp Grid and can be viewed by any role with
access to the Analyze page and the associated custom pages.
· If more than one page has this checked, they
will display in the Dashboard dropdown.
8. Include
Employee Header
Action: Adds a row
at the top of the page to pull in fields from the Employee or Employee Comp
Cycle Object
· Only available with Sidebar layouts and
Employee Comp Cycle as the base object
· For time series fields from the Employee
Object, the most recent value is pulled. It does not follow the comp cycle
selection on the page.
Additional features:
· Include photo in
header – displays the employee’s photo, if uploaded
· Append employee
name with ID # - includes the employee’s Name and ID at the top of the page
9. Sidebar
Apply
filters from Comp Grid page: For sidebar pages with a base object of
Employee Comp Cycle, you can check this off to keep the filter setup on the
comp grid when you navigate to a custom page.
Apply
page-level filters: Filters the number of records available in the
sidebar. You can set a sidebar filter on the admin side that is defaulted to
all users with access to the page. Fields available in the filter list are
limited to the side bar base object.
Allow
filtering by user: Gives the end user access to add additional sidebar
filters or remove the default filter set on the admin side. Setting a default
filter is optional. If none is set, the filter hyperlink simply appears
available to be used when needed.
10. Apply Page-Level Components Filters
Action: Set a filter
on the admin side that is applied to all widgets on the custom page for all
users. Fields from all objects can be used in the filter. Most applicable for
pages designed to show aggregated data where you wish to apply filters to the
data populated by the page components. This is commonly used if you want to
exclude certain comp cycles from showing in widgets that display history.
Allow
filtering by user: Gives the end user access to add additional page
filters or remove the default filter set on the admin side. Setting a default
filter is optional. If none is set, the filter hyperlink simply appears
available to be used when needed.
11. Show Component Borders
Actions: Separates widgets into their own sections