Skip to main content

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

Supported actions and limitations in AJAX containers

Updated on December 13, 2022

Use AJAX containers to render and control multiple harnesses in a single browser window and eliminate the use of iframe tags in your markup. To use the full potential of AJAX containers, learn about the supported actions and limitations of this tool.

Supported actions

AJAX containers support the following work-related actions:

  • Create new work
  • Open assignment
  • Open work item
  • Open work by handle
  • Display harness: new document
  • Open section

For more information about actions, see Available UI actions.

Unsupported actions

AJAX containers do not support the following actions:

  • Display harness: replace current
  • Open wizard
  • Open landing
  • Open work by URL
  • Get next work
  • Open rule by class and name
  • Open rule by keys
  • Refresh from outside the AJAX container


AJAX containers have the following use-case limitations:

  • AJAX containers support UI in template mode only.
  • You cannot use many AJAX containers of the same kind in the same document. For example, the same document cannot include two primary AJAX containers.
  • AJAX containers cannot be nested.
  • Container components, such as modal dialog boxes and overlays, do not support AJAX containers. For example, you cannot use AJAX containers in a flow-action section that is displayed in a modal dialog box.
  • When an AJAX container is opened as a modal (tertiary AJAX container), the action set that includes triggering an openwork action by clicking a link must be disabled in that container. If the action set remains active, a click on the action set link triggers background operations while the AJAX container remains open, causing potential issues.

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