Guidelines and Limitations for Master/Detail Components

Note the following guidelines and limitations for target content and master/detail components:

  • For a fluid component to be included as target content, it must be defined as a Standard fluid component.

    Important:

    A fluid wrapper component (that is, a fluid activity guide, another master/detail component, or fluid navigation collection) can never be included as target content inside a master/detail component.

  • Typically, for each page defined within the fluid component, the outermost group box must include the ps_apps_content style or another styling appropriate to the page design.

  • Unless AJAX transfers are enabled on the master/detail component, the fluid component should not perform a transfer to another component. This includes transfers via a hyperlink, a push button, or a PeopleCode program. Such transfers will result in the user exiting the master/detail component. See AJAX Transfers for more information.

  • If the target content is a fluid component that employs an internal two-panel construct (that is, it either includes a Side Page 1 page, was built from the PeopleTools 8.54 PSL_TWOPANEL layout page, or was designed with an internal left panel similar to PSL_TWOPANEL), you must enable left panel collision handling with the slide-out left panel on the master/detail component. See Left Panel Collision Handling with Slide-out Left Panels for more information.

  • The fluid component must have the search page type set to None to be displayed directly as target content within a master/detail component. Otherwise, if the search page type is set to Standard or Master/Detail, the fluid component cannot be displayed as target content within a master/detail component. However, a link for the component can be included in the navigation list as long as the link destination is programmatically set to a new window or to replace the current window. See PeopleCode API Reference: SetGroupletDisplayIn method: Field class.

  • The fluid component definition must not include a Header Page page definition.

  • Including a Footer Page page definition within a fluid component displayed as target content inside of a master/detail component may or may not follow usability standards and could create a confusing user experience.

  • To use a multi-page fluid component in a master/detail component, you can do one of the following to maintain a clear and consistent user experience:

    • Reparent the page tabs to a group box of type Page Tab that is included on each page definition.

    • Include PT_SIDE_PAGETABS in the component definition to reparent the page tabs to the left panel. You must also enable left panel collision handling with the slide-out left panel on the activity guide. See Left Panel Collision Handling with Slide-out Left Panels for more information.

    • Hide the page tabs. You can do so in the component definition by deselecting the Display Folder Tabs (top) on the Internet tab. Alternatively, you can use delivered styles to hide the page tabs.

  • If you want the master/detail component to maintain the same title in the fluid banner regardless of which page is displayed as target content, then set the title in whichever definition generates the content for the master list using the PeopleTools-delivered SetSideTopTitle JavaScript function. For example:

    AddOnLoadScript("SetSideTopTitle('" | EscapeHTML("My M/D Component's Title") | "');");

  • If your master/detail component controls the title in the fluid banner (see the preceding bullet item), for each page defined within the target component, you should include a group box of type Page Title that is defined to be visible when the page is rendered within a master/detail component. This Page Title group box provides context that is lost when the page title is not displayed in the fluid banner. To hide this page title if the page is rendered outside of a master/detail component, use the psc_hideinmode-notmd style.