The vmiactions table stores data about actions performed by recipients in response to messages sent from Vocera Messaging Interface clients.

This table has a unique key based on the TxMillis column.

Table 1. vmiactions table
Column Description

bigint(15) unsigned NOT NULL default '0'

The TxMillis column gives each row in the table a unique identifier. The value represents the number of milliseconds since January 1, 1970 (a date specified for internal use by the report system). Because of the uniqueness constraint, it may not reflect the exact actual date and time of the event. See TxDateTime.


datetime NOT NULL default '0000-00-00 00:00:00'

The TxDateTime column stores the date and time of an event, accurate to the second.


date default NULL

The TxDate column stores the date of an event, accurate to the day.


varchar(50) NOT NULL default ''

The unique ID of the Vocera Messaging Interface client.


bigint(20) unsigned NOT NULL default '0'

The Vocera Messaging Interface message ID, which must be unique for the client.


varchar(20) NOT NULL default ''

Specifies which type of Vocera entity (for example, user or group) received the message.


varchar(50) default NULL

In a multi-site installation, the RecipientSite column specifies the Vocera site with which the recipient is associated. In a single-site installation, this value is null.


varchar(70) NOT NULL default ''

Specifies the ID of the message recipient.


varchar(100) default NULL

Specifies the name of the message recipient.


varchar(50) NOT NULL default ''

Specifies the type of action. Sample values include: Accepted, Rejected, Delivered, Read, and Response.



Specifies detailed information about the action. For example, if the action type is Response, the response could be OK, Busy, or Cancel, which would appear in the ActionDetail column. If the action type is Rejected, the ActionDetail column might show "User is not logged in" to explain why the message was rejected.