How can the correct `tree/` navigation URL be derived for a specific tree-enabled screen (like a custom navigator), when there's no documented list mapping screens to their tree URLs?

Q: How can the correct `tree/` navigation URL be derived for a specific tree-enabled screen (like a custom navigator), when there's no documented list mapping screens to their tree URLs?

A tree navigation URL follows the pattern tree/ / — tree is always the literal page-type prefix for tree URLs, and the and values can be read directly off the target screen's own URL when you navigate to it normally (look for its treeclient= and treeview= parameters in the address bar) rather than needing a lookup table; taking those two parameter values from a real navigation to the tree-enabled screen and plugging them into the tree/ / pattern reliably reconstructs the correct Lobby navigation URL for that screen.

Answer

A tree navigation URL follows the pattern tree/<treeclient>/<treeview> — tree is always the literal page-type prefix for tree URLs, and the <treeclient> and <treeview> values can be read directly off the target screen's own URL when you navigate to it normally (look for its treeclient= and treeview= parameters in the address bar) rather than needing a lookup table; taking those two parameter values from a real navigation to the tree-enabled screen and plugging them into the tree/<treeclient>/<treeview> pattern reliably reconstructs the correct Lobby navigation URL for that screen.

← Browse Platform, Aurena, and customization questions