Viewing triggered events

An event is triggered when the conditions described by the event are met at the point in a study described in an associated target.

An event is processed when an associated action (such as sending an email) is performed. Processing may be successful or unsuccessful.

The Subject Event Viewer displays details of all triggered events. You can choose to see unprocessed events (current events) or processed events (audit trail).

Searching for events

To find all triggered events of a particular type, select from the Event type and/or Target type lists. The From status and To status relate to the type of event, (if it involves changing from one status to another). The Visit code, eForm code and Question code all relate to the type of target, if applicable.

To find a particular event, enter the unique code into Event code. You can choose to restrict the results to a particular study/site/subject.

To find all events with a particular status, enter the status code into Event status. For example, to find all events with a 'Send Email' action that has failed, enter '-1' into the Event status. To find all events with a 'Send Email' action that has succeeded, enter '1'.

The standard event status codes are as follows and apply to all triggered events:

Code	Description
0	Unprocessed action
Any positive number	Action processed successfully
Any negative number	Action processing failed

For example, MACRO's built-in event email system uses '1' for a successful attempt at sending an email and '-1' for an unsuccessful attempt.

If you are using the API to directly update the database tables, you might choose to design your own processing codes using specific numbers to give more precise detail about the stage of processing for an event. In this case, you can assign any numbers you choose as long as you use positive numbers to indicate success and negative numbers to indicate failure.

Unprocessed events (with status 0) are held in the EVENTDATA table and correspond to the events you see when searching for 'Current events' in the Subject Event Viewer. Events remain in this table until processing is successful. Processing can be automatic (when an associated action such as sending an email is performed) or manual (when data is manipulated via the API).

Once processing has been attempted, the event will be moved to the EVENTDATAHISTORY table which acts as an audit trail. Events from this table correspond to the events you see when searching for 'Audit trail' in the Subject Event Viewer.

For example, if an event with a 'Send Email' action is triggered and the email fails to send on the first attempt but is sent successfully on the second attempt, the EVENTDATAHISTORY table will contain three rows for that event. One shows the details of the unprocessed event (0), the second row shows the failed attempt (-1) and the third row shows the successful attempt (1).

Select 'Current events' to see all unprocessed events and those with a negative status (for the Send Email action, this will represent a failed action).

Viewing the search results

The timestamp column shows the database time that either the event was triggered (for an unprocessed event) or the time that the processing attempt took place.

Information about event processing attempts is displayed in the Message column, for example a reason for an email not being sent. If an event email has been successfully sent, it will show the email recipient, subject and body text. Note that for events with an email action defined, Arezzo expressions are evaluated at the time of the email being sent rather than the time the data was saved in the database. This means that the email content will be accurate to the time of sending.

Re-running actions

You can choose to re-run processing for single or multiple events by selecting the events to re-run and then clicking the Re-run event actions button at the bottom of the screen. Re-running an event action for an event with an associated email will have the effect of attempting to send the email again.

A popup window shows the result of the re-run along with any reasons for failure. Click OK to close the window.

Although failed events can be displayed in the Subject Event Viewer, there is no other notification of them so regular checks should be made.

You can only re-run actions for current events. You cannot re-run actions for events in the audit trail.

Changing the status of an event

If you wish to change the status of an event manually, select the event and click the Change Event Status button at the bottom of the screen.

Enter the new status and an optional message explaining the reason for the change and click OK.

You can only change the status of a current event. Events in the audit trail cannot have their status changed.