Limitations

Please note the following limitations on developing and using activity guides:

• If the user accesses and updates a transaction directly (for example, through standard menu navigation) rather than through the action item link in the activity guide pagelet, then any status change effected there will not be reflected in the activity guide pagelet.

• If an action item is linked to an external URL (that is, a non-PeopleSoft URL), then you must provide a custom button to allow the user to mark the action item as complete.

• Do not link an action item to a multistep transaction such as a transaction that represents a wizard (for example, Pagelet Wizard).

• Activity guides support a two-level hierarchy only—that is, only one level of detail is supported beneath a summary action item.

• In custom action buttons, do not attempt component buffer access, use think-time functions such as MessageBox, WinMessage, or others, or use system variables. See Developing Custom Action Buttons.

• Do not configure a remote activity guide pagelet for use in a WorkCenter defined on the local node. Instead, define both the WorkCenter and activity guide pagelet on the remote node. Then, using unified navigation or another mechanism, access the content reference for the remote WorkCenter from the local node.

• The Related Content frame configured for a classic page will not be displayed when that page is rendered inside any fluid wrapper, such as in a fluid activity guide or in the fluid master/detail container.

• Activity guides and fluid navigation collections do not support conditional navigation.