Guidelines for Merged Homepages and Dashboards in a Cluster

The rules that govern the merging of homepages in a cluster also apply to the advanced sectionalized homepages, dashboards, and sections.

The merging of dashboards depends on the following three conditions:

  • The dashboard label should be the same.
  • End-user personalization should be disabled.
  • The CREF attribute, CLUSTER_AWARE, should be set to True.

Dashboards must meet all the three conditions to be eligible for merging.

In a merged homepage or dashboard, the following guidelines apply:

  • If the Uses Custom Layout setting is specified for any of the homepages or dashboards, the Uses Custom Layout setting is automatically applied to the merged homepage or dashboard.

  • If the Hide Notification Panel setting is specified for any of the homepages or dashboards, the Hide Notification Panel setting is automatically applied to the merged homepage or dashboard.

  • The custom style sheets (defined using the PS_STYLESHEETS content reference attribute) from all the homepages or dashboards are collected and appended to the HTML <head> tag of the merged homepage or dashboard HTML document.

  • The custom style classes (defined using the PS_STYLECLASSES content reference attribute) from all homepages or dashboards are merged together and set in the HTML <div> tag of the merged homepage. Duplicate style classes are automatically removed.

  • PeopleTools automatically adds a style class called node-<name of the node>, for example, node-HRMS, depending upon the application node where the first homepage or dashboard was processed. In a merged homepage or dashboard where the participating application nodes are HRMS, ERP, CRM and the acting portal node is HRMS, then the style class name is node-HRMS because the first homepage or dashboard was processed on this node.