Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Linking a landing page to an application guide

Updated on April 5, 2022

Link a landing page to your application guide to give users direct access to internal tools.

  1. Open an application guide by searching for it or by using the Application Explorer.
  2. On the Definition tab, expand a chapter in the Chapter name column.
  3. Click the Gear icon next to a task name.
  4. Add a link to the task.

    Tip: For an example configuration of the following fields, open the Pega-Landing.pyMainMenu navigation rule by searching for it or by using the Application Explorer.

    1. In the Action type list, select Open landing page.
    2. In the Display text field, enter a label for the link that users click in the task.
    3. In the Action field, select Display.
    4. In the Name field, enter a label for the tab that displays the landing page.
    5. In the Class field, press the Down Arrow key, and then select a class that defines harnesses.
    6. In the Harness Name field, select the harness that the landing page displays.
    7. Decide which tab has focus when users open the landing page.
    8. Enter the tab name in one of the following fields, based on the tab's position in the landing page hierarchy:

      • Level A

      • Level B

      • Level C

  5. Click Submit.
  6. Click Save.
  • Previous topic Linking a help topic to an application guide
  • Next topic Linking a custom section to an application guide

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us