---
title: UserActions component for Visualforce components (Deprecated)
slug: '1216'
canonical_url: https://docs.coveo.com/en/1216/
collection: coveo-for-salesforce
source_format: adoc
---
# UserActions component for Visualforce components (Deprecated)
> **Deprecated**
>
> This feature is still available, but no longer supported as of the August 2023 release of Coveo for Salesforce version [5.2](https://docs.coveo.com/en/n5bj0150#august-2023-release-v5-2-initial-release).
The `UserActions` component allows your agents to see the actions performed by the end user before or after the creation of a case within the Salesforce console.
The component takes the information from the [Coveo Analytics](https://docs.coveo.com/en/182/) events performed during the visit in which the case was created, as seen from the [Visit Browser](https://docs.coveo.com/en/274/) page of the Coveo Administration Console.
You can configure which events the component displays.
See [Review user visits with the Visit Browser](https://docs.coveo.com/en/1964/) for details on this page.
The component typically appears in a tab of the Insight Panel, but can also be included as a standalone component in a Visualforce page.
See [Implementing the UserActions component](https://docs.coveo.com/en/1101/) for more information.
> **Important**
>
> The analytics transactions are processed at least at a 15-minute interval, or at a shorter time interval whenever a sufficient number of events to process are available.
> There may therefore be a delay of up to 15 minutes between the moment an event is performed and the time the event appears in the component.
> The delay however decreases as the rate of search events increases.
> **Note**
>
> In Health Insurance Portability and Accountability Act (HIPAA) environments, the `UserActions` component may display Personal Health Information (PHI), per normal usage.
> However, no data is stored in Salesforce.
> The data that's returned by the `UserActions` component follows the same security rules as the Coveo Search component.
## Option
### showButton
Specifies if the component should render a button to open/close itself.
The default value is `false`.
```xml
```
### enableBindOnBox
Specifies if the component should listen to the `onPopupOpen` event fired by the closest `BoxPopup` component to open itself.
The default value is `true`.
```xml
```
### filters
Specifies which events the `UserActions` component should display.
You typically want to include only events that are manually performed by the end users, including appropriate custom events, and omitting the ones that are generated automatically by the components.
They typically are the Click, Search, or Custom [dimension](https://docs.coveo.com/en/1904/) causes.
The default value is `searchboxSubmit,documentOpen,documentQuickview,pageVisit,pageView,caseCreate`.
```xml
```
Where you can replace `` with the specific events you want the `UserActions` component to display.
## Method
### open
This method opens the `UserActions` component.
```javascript
$('#myUserAction').coveo('open')
```
### close
This method closes the `UserActions` component.
```javascript
$('#myUserAction').coveo('close')
```
### toggle
This method opens or closes the `UserActions` component, depending on its current state.
```javascript
$('#myUserAction').coveo('toggle')
```
## Usage
### Adding the `UserActions` component as a Tab in the CoveoBox Panel
The `UserActions` component is typically included in the tab of a `CoveoBox` panel, as follows:
**Sample**
```xml
```
### Adding the `UserActions` component as a Standalone Component
To make the `UserActions` component work as a standalone component, you need to add the [UserActions Visualforce Component](https://docs.coveo.com/en/1188/) in your Visualforce page.
You also need to create a custom handler to open/close the component or you can use the `showButton` property.
**Sample**
```xml
```