User Actions Dashboard
The User Actions dashboard contains data about user events (that is, who did what and exactly when).
In addition to the numerous panels that can be created for the User Actions Dashboard, this dashboard contains an Audit Trail Log A user's activity is logged for 31 days in the Audit Trail Log panel. After 31 days the activity in the Audit Trail Log is deleted.
User Actions records can contain data associated with one or more of the following fields (Audit Trail log):
|requestID||keyword||Used to track specific API requests (for example, customer scripting troubleshooting purposes). This field contains the Request ID. The Request ID can be provided via the x-request-id header in the API CX Contact request. The Request ID must be generated by the client and can be used to track specific API requests (for example, for customer scripting troubleshooting purposes).|
|@timestamp||date||The date/time when an action started (for example, when the request arrived in the system).|
|userName||keyword||The login user name that initiated the logged action.|
|@endtime||date||The date/time when the action was completed.|
|duration||integer||The duration of the action (@endtime - @timestamp) in milliseconds.|
|action||keyword||EDIT | DELETE | ALTER | LOGIN | LOGOUT | EXECUTE | SEARCH | READ | TEST
|actionDetails||keyword||Provides additional details about the action. These values are dependent on the CX Contact object or entity.
|objectType||keyword||The type of object. For example, Campaign Group, Contact List, Suppression List, Time Zones Map, Compliance Rule, List Rule, List Automation, and so on. For details, refer to the Object Types and Related Sub-types section.|
|objectSubtype||keyword||A sub-classification of the object type. For example, Attempt Rule, Location Rule, Filtering rule, Selection Rule Contact, Upload Rule Contact, and so on. For details, refer to the Object Types and Related Sub-types section|
|objectName||keyword||The name of the object as stored in CME.|
|objectID||integer||DBID of the object as stored in CME.|
|apicall||boolean||Appears as True if the executed action is performed via an API call and False if the executed action is performed via the user interface. This field enables you to see if a change was manually performed by a user or automatically by the system. For example, if the change was manually performed by a user the apiCall is false and if the change was automatically made from a 3rd party system or external system using an API call to run the command remotely the apiCall is true.|
|successful||boolean||Appears as True if the action was completed successfully and False if the action was not completed successfully.|
|errorMessage||text||An error message (as displayed in the user interface or returned as an API response) when the request execution was not successful.|
|details||text||An additional textual description of the action when available.|
|endPoint||text||The API end point that was called.|
|changeSet||object||Contains details about what was changed (for example, a new option value, a new dialing mode, and so on) in JSON format. Note: The Change Set is only stored when the changes are successful and only for objects represented in CME (for example, EDIT action).|
Object Types and Related Sub-types
|Object Type||Object Sub-types|
|Time Zones Map|