Extended capabilities for the Asset Manager!
The Asset Manager now includes the capability to search, view details, download, delete, and upload programming Hooks for modifying screens in Replay.
You can use the Hooks feature to align page content and modify fonts and colors on the screens in Replay.
You can notify Alert recipients via Slack!
The IBM Tealeaf on Cloud Alert feature is integrated with the cloud-based collaboration tool Slack.
Previously, Alerts were sent to recipients by email only. With the Slack integration, recipients can be alerted in a specified Slack channel.
Here’s how it works:
If you want to send notifications to Alert recipients via Slack, you must configure Slack first as follows:
Note: For more detailed instructions, consult Building Slack apps in the Slack documentation.
- In Slack, create a Slack App and select a workspace.
- Go to OAuth and Permissions feature in Slack and find the area where you specify Scopes.
In Slack, Scopes define the API method that your Slack App can call.
- In the field where you select permissions and scopes, select the following permission scopes.
- Click Save to save the permissions and scopes to your Slack App.
- Install the App and submit a request for approval.
When the request is approved, and the App is installed, go back to the OAuth and Permissions feature for the App to retrieve the OAuth Access Token.
- Click Copy to copy the OAuth Access Token.
- In IBM Tealeaf on Cloud, go to the Company Settings page and paste the copied token into the OAuth Access Token field.
Now you just need to configure the Alert in IBM Tealeaf on Cloud to send notifications via Slack.
Here’s how you do that:
Use the Alert Manager to create a new Alert or edit an existing Alert.
On the Recipient information page, select the Slack check box and enter a Slack Channel name.
Note: IBM Tealeaf on Cloud does not support private slack channels currently.
Finish and save your changes.
A quick and easy way to audit Tealeaf on Cloud user activity
Administrators can use the Audit Log to monitor and track user activities (views, searches, edits, deletes, and replays) initiated against data objects, such as reports, Events, sessions, and workspaces.
With the Audit Log, administrators gain insight into how and when users interact with data objects.
Here’s how it works:
From the menu bar, select Audit Log tab. and then select the
Select the date range for which you to view user activity and click Apply to see a list of user activities.
- rearrange the column order
- sort column content from ascending to descending order, and vice versa
- search the contents of the table
- export the contents of the Audit Log to a CSV file.
Usability enhancements to IBM Tealeaf on Cloud and CX Overstat on Cloud
Changes to filtering on the Session Search list
Column filters and sort order are cached, and the Save to view option is removed from the filter dialog.
Now,when you apply filters to the Session Search list, and then exit the list, the filters are cached. When you to return to the Session List, the filters you set remain active. The cached filters are applied even when you change the search criteria.
An option to Clear all filters is added to clear filters from the Session List cache.
Previously, if you wanted to preserve Session Search filters, you set the Save to view option before leaving the session list page. If you forgot to remove the filter, it was applied to future searches, sometimes unbeknownst to you, which might lead to an inaccurate interpretation and assessment of the results.
The total number sessions that match the search criteria is noted on the Session Search list
Session Searches have a display limit of 2500 sessions, even though there might be more occurrences of the search conditions for the time criteria specified.
With this enhancement, you can see the exact number of occurrences that match your search conditions, even when the number exceeds the 2500 cap on viewable sessions:
Knowing the number of occurrences can help you assess the impact of an issue without having to run multiple searches.
Alphabetized search criteria and condition lists
The search criteria and condition lists in Session Search are alphabetized.
Alphabetized lists help users to quickly find the application they are looking for in the App profile field, and to find and set search conditions quickly and easily.
A more direct way to access the Edit mode for Events and Event data objects in the Event Manager
You can double-click Events and Event data objects (Hit attribute, Session attribute, Step attribute, Dimension, or Dimension group) in the Event Manager, and go directly in to the Edit mode.
Previously, you had to select the Event or Event data object, and then click Edit.
Validation is added to the regex field for Hit Attributes and Step Attributes
When you enter an expression in the regex field for a Hit Attribute or Step Attribute, the data that you enter is checked for validity.
Previously, users could enter and save regular expressions that were invalid.
Quickly find the screens or steps that contain matches from session search
If a screen or step in the session contains a match of the search conditions you specified, it is marked with a blue flag in the navigation pane of Session replay.
The visual cue makes it simple to identify areas of interest in the session and can be especially helpful when you are analyzing sessions that contain many screens and steps.
A more meaningful way of assessing visitor interaction with radio buttons on a form
Forms can present users with options by way of radio buttons.
In some cases, all you want to know is that the visitor answered the question by selecting a radio button. You don’t particularly care which answer they provided. In such cases, it makes sense to treat the group of radio buttons as a single element on the form. By treating a group of radio buttons as a single form element, you ascertain how many visitors interacted with the question, rather than the answer they provided.
For example, you might have a section of a form that has a radio button list for a person’s title ( Mr, Mrs, Ms, Miss, Dr.)Previously, each option was treated as a separate element on the form. However, for such information, the analyst is more interested in knowing that a selection was made, rather than which selection was made.