Event manager processing of step-based event objects

You can create step attributes through Request view in Browser Based Replay.

Note: Creation of step attributes is not supported in RTV.

When you create objects through Browser Based Replay, the Event Manager checks to see if the selected content is already referenced in an existing event object. If so, the Event Manager selects that object for you to edit.

In some cases, the selected event object is provided by Tealeaf® and is therefore not editable. For example, Tealeaf provides the CUI Hit hit attribute, which references the contents of the HTTP_X_TEALEAF request variable. When you choose to create attributes or events from the values of this request variable, the Event Manager selects the CUI Hit attribute for you to edit. This hit attribute cannot be edited.

Note: If you want to create more step attributes and events from session data for which attributes or events are already created, you must create them manually through the Event Manager.

Note: There is a known issue in which the PCA fails to properly recognize UTF-8 encoding in data that is submitted from client frameworks, and the data can be mangled in the stored session, causing issues in eventing and search.

Note: The following information applies to IBM® Tealeaf version 9.0A only.

9.0A can properly recognize UTF-8 encoding in data that is submitted from client frameworks.

Permissions for creating step-based event objects

To create step attributes, you must have permissions to access the Tealeaf Event Manager, where event-related objects are created in the Portal.

To test access, select Configure > Event Manager