Adding an AJAX container to a portal

Give your application a clearer structure by specifying areas for main, secondary, and additional information.

Like a dynamic container, an AJAX container defines where documents, such as work items and cases, load on the screen. However, AJAX containers are not tied to a specific panel or a screen layout. This type of container also supports conditional logic, such as when rules, and can be configured for use in different roles. You can also have up to three AJAX containers in a harness.
Note: If you create a portal in App Studio, Pega Platform generates a dynamic container automatically.
  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the User Interface category, and then click Section.
  3. Open the section to which you want to add the AJAX container.
  4. If the editing options are not visible, click Convert to full section editor.
  5. On the Design tab, expand the Structural list, and then drag the AJAX container onto the design canvas.
  6. In the AJAX Container Settings window, in the Type list, select the type of the container:
    • To set the container as the default destination for documents, select Default.
    • To set the container as a destination for secondary documents, select Secondary.
    • To set the container as a destination for supplementary documents, select Tertiary.
  7. In Default view, select the view that you want to display when the application starts:
    • To display an empty container, select None.
    • To display a section, select Section, and then provide the page context and the section name in the fields below.
  8. To use tab navigation between multiple documents, select the Show as tabs check box.
  9. In Maximum Documents, define the number of documents that the container can hold.
What to do next: If you set your container type to Secondary or Tertiary, configure the section that you want to load in the container by creating an action set. For more information, see Adding actions to a control.