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.

Configuring a screen layout

Updated on April 5, 2022

Determine the purpose of each area of the screen layout and identify the section to be placed in each area.

Before you begin: Ensure that you follow the steps in Harness form Adding a screen layout.
  1. Open the harness that you want to modify.

  2. Click the Screen layout, and then click the View properties icon.

  3. On the General tab, select a screen layout format, such as Header footer right, and click Submit.

  4. On the Harness form, drag a section into each region of the screen layout and complete the property panel for each region of the screen layout.

  5. Optional:

    To allow users to resize the screen layout, select the User resizable check box on the Panel properties dialog box for the appropriate regions in the screen layout.

  • Harness form Adding a screen layout

    Screen layouts determine the overall structure of your screen. They define the structure of a harness that is included in a composite portal. When you create a new harness it contains a screen layout by default. A harness can contain only one screen layout.

  • Screen layout properties

    Some layout properties might not be available if the harness is used as an app view, main area, inner harness, or page view.

  • properties panel

    Click the View properties icon in the header of the region of the screen layout to display the Properties panel for that region.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us