Configure Landing Pages

About Landing Pages

Landing Pages were designed to eliminate complex navigation paths by providing an 'action oriented' experience that puts users in the drivers seat. Key features include:

  • Hero Text to keep you up-to-date and informed 
  • ability to pin Action as Favourites
  • ability to find Action quickly using Tags and Quick Search

As the name suggests, Users are automatically taken to their personalised Landing Page as soon as they log-in.  Landing Pages provides Users with:

  • direct access to the: Screens, Reports, Forms, Charts, and Boards that are relevant to their role (useful for infrequent tasks).
  • a carousel of  Hero Texts to keep an eye on the things that matter the most.

Out of the box, the Landing Page for tenant Administrators has a Hero Text to show how many tasks are outstanding, and a Action configured as a Nav Item opens the Administration area.

Things you should know

  • Landing Pages are opt-in 
  • you should configure Landing Pages prior to enabling 
  • when enabled, Landing Pages replaces the Classic Home Page
  • enabling Landing Pages is a tenant wide setting
  • you can enable / disable Landing Pages at any time
  • Landing Pages will not override existing 'default login location' settings

Configuration options

There are two parts to the Landing Page - Hero Texts at the top and Action at the bottom.  Configuration for both is similar, however Hero Texts have a few extra steps. The following table provides an overview of the Landing Page configuration options. 

 Hero TextAction
Config ItemCreateEditNavViewCreateEditNavView
Name    Name: the text that is displayed on the Hero Text or Action YYYYYYYY
Description    Description: for Administrator use, the description is not displayed to users on their Landing PageYYYYYYYY
Tags     Tags: short semi-descriptive 'tags' that can be used to find specific Actions. Tags apper on the User's Landing Page----YYYY
Nav Item      Nav Item: a destination that the user will reach when they click on the Landing Page or Action  --Y---Y-
Object    Object: the Object that will be used for creating a new Record  Y---Y---
Report    Report: Select a Report in order to filter Forms that can be used to create, edit, or view a Record-Y-Y-Y-Y
Form    Form: the Form that is used to create, edit, or view a RecordYY-YYY-Y
Hero Report   Hero Report: the Report that provides data for a Hero TextYYYY----
Hero Column   Hero Column: the column from a Report that provides data for the Hero TextYYYY----
Hero Method   Hero Method: the method used for aggregating report data to display in the Hero TextYYYY----

Strategy for configuring Landing Pages

Each user's Landing Page is automatically customised according to the Roles they belong to. Landing Pages can be further customised for groups of users (or even an individual) by creating additional roles. 

The following outlines a 3-step-process to setup Landing Pages in a way that is consistent, quick to implement, and easy to manage.  The basic steps, explained in greater detail in the following sections, are:

  1. initial setup
  2. create a like-for-like version of the classic home page
  3. add Hero Texts and Actions

Initial setup  

Initial setup involves setting up a helper Role and a helper User to view the configuration holistically.

  1. Create a new role for your tenant - this will be "a dummy role that should not be given to any real user, purpose is to provide a holistic view of the Landing Page configuration".
    1. name the role 'lp_config'
    2. add a description (e.g. text above: "a dummy role...")
    3. in the 'Member of' tab click on the 'link to existing' & select 'All' --> Ok --> Save

  2. Create a new User for your tenant - this will be "a dummy user that should remain disabled, purpose is to provide a holistic view of the Landing Page configuration".
    1. name the user 'lp_user'
    2. add a description (e.g. text above: "a dummy user...")
    3. disable the user: status = disabled
    4. in the 'Security roles' tab click on the 'link to existing' & select 'lp_config' --> Ok --> Save

  3. Test - open the Landing Page configuration tool and view the configuration for all users:
    1. enable 'View as user' mode
    2. select user: lp_user (the Landing Page user preview will load to show all configuration options)  

Create 'like-for-like'

Create a new role  for each Application in your tenant. The purpose of these roles is to provide Navigation Access to the corresponding Application.

  1. Add & configure a new Role for each Application 
    1. identify an Application to configure and create a role: e.g.:  lp_AppName
    2. in the 'Member of' tab add every other role that is related to the Application
    3. in the 'Navigation Access' tab, select the Application and 'check' the top level folder

  2.  Setup the new Role in the Landing Page configuration tool
    1. In 'Configure role' mode, select the role, e.g. lp_AppName
    2. In the 'Actions' window: click 'New' --> a menu appears, select: 'View navigation item'
    3. Enter the text that should appear on the Action in the 'Name' field
    4. Enter a description to help you remember what this configuration is, e.g.: Navigation to root application for lp_AppName
    5. Enter tags to help users find this application
    6. In the Nav Item picker, select the corresponding top level folder for the application (e.g. lp_AppName)
    7. Click 'Ok' then 'Save'

  3. Test and repeat until all Applications are represented as Actions on the Landing Page
    1. Click 'view as user' and select user: lp_user
    2. Confirm the configuration 
    3. Repeat 1 & 2 until each Application has been added