Algorithm for finding "home"
Portal traverses pages and labels until it finds the first XDIME page that the user is allowed to see.
Labels may not be selected, and deactivated pages are treated like labels.
Traverse proceeds depth first
starting at Content Root as shown in the following example:
Label 2A1a (not XDIME)
Label 3A1a (deactivated)
Label 4A1a (XDIME activated and user has permission to view)
Label 5A1a (not selected and not visible)
When creating the XDIME portal navigation with the XDIME aggregator JSPs provided with Mobile Portal Accelerator, it is mandatory that all XDIME related labels, pages, and URLs be created under the Content Root
label. XDIME pages created outside of Home should be used for administrative purposes or will require custom XDIME aggregator theme JSPs to display them.
In the Label 1 section, nothing is selected.
The Label 2 section is not selected because there is no XDIME supported code.
The Label 3 section is not selected because Page 3A1a is deactivated.
Page 4A1a is selected as "home" or "root" because it contains XDIME code and the access control for that file has been set up so the user has permission to see the file.
The Label 5 section is not selected and is not visible because Page 4A1a has already been selected as "home".
Parent topic: Using the XDIME aggregator