The persistent header bar always shows the Burger menu, Search, Quick links, and Signed-in Users.
The burger button toggles the global menu open and closed. The menu remains unchanged during a user's session, but it might contain links to other pages within the app or external links to other websites. Each link is subject to role-based access control. To configure the global menu, please take a look at our knowledge base article, Burger bar global menu.
The search has very powerful indexing and faceting configuration options. Users can search and find content, for example, People or Jobs. Please take a look at our knowledge base article, Search.
Quick links can contain a link to the Worklist, showing a badge count for open notifications, a link to Edit the page, only visible to superusers, or a link to perform diagnostics on the page, only visible to users with diagnostics enabled.
This is also a global menu that generally remains unchanged during a user's session. Users can sign in and out or quickly go to the homepage. If you would like more information, you can see our knowledge base article, User menu.
So your app feels familiar to your users, you can add your logos and app icons. You can use your own brand's color scheme and embed videos, images, adverts, and other assets in various places throughout your app. You can also include live news and a Twitter feed. If you'd like to find out more, you can see our knowledge base article, Using a branded theme.
This header appears for most HCM pages and includes the photo of the person it's about, options to change the image, subject to access, their current availability, name, job title, and a list of Context actions.
For HCM pages, the header appears when the signed-in user has permission to view the Applaud show person menu context (XXAS_SHOW_PERSON_MENU_CTX) for the person they're looking at (the Applaud HR Person data object). It gives you fine-grained control to show or hide as you choose. For example, you could hide it when looking at yourself but show it when looking at anyone else's profile.
To configure the content displayed within the context header, please see:
These are a list of actions or links shown in the context header. In HCM pages, these are contact numbers or email addresses. To configure contact numbers, please take a look at our knowledge base article, Contact numbers.
A sub-navigation menu appears relevant for the current page. Each link is subject to role-based access control. Please take a look at our knowledge base article, Submenus.
A page is a container for the content represented as one or more blocks. A page is not a static HTML page defined in the configuration. New pages can be added, changed, and removed dynamically without writing code. A page can be optionally added to the burger, user, or sub-menu menu. A page is visible if any of its blocks are accessible. Please take a look at our knowledge base article, Pages.
A block displays configured data on a page. There are many different blocks available, each having other characteristics and behaviors, for example, a list, chart, and form. In addition, you can control the visibility of each block with access controls. If you would like more information, you can see our knowledge base article, Overview of a block.
As illustrated, you can open a page in a modal window or as usual. Like any other page, a modal window might display one block or multiple blocks.