UNICOM Intelligence Interviewer - Server Admin audit trail

UNICOM Intelligence Interviewer - Server Admin uses the following tables to generate an audit trail of who has used the system, when, and what activities they used. The tables are created in the mrUserData database when you install UNICOM Intelligence Interviewer - Server Admin.

Table	Description
UserSession and UserSessionHistory	Who logged in to UNICOM Intelligence Interviewer - Server Admin, when and for how long.
ApplicationSession and ApplicationSessionHistory	Who used UNICOM Intelligence Interviewer - Server Admin activities and when.
CatiInterviewerSession and CatiInterviewerSessionHistory	Which interviewers used Phone Participants and when, plus information required for interviewer monitoring, such as number of contacts made.
CatiInterviewSession and CatiInterviewSessionHistory	Information about all telephone interviews conducted.
CatiSupervisorSession and CatiSupervisorSessionHistory	Who monitored which interviewers and when.

The tables work in pairs: The first table in each pair records information about current sessions; the second table in each pair records historical information about past sessions. For example, records in ApplicationSession tell you who is currently running an activity in UNICOM Intelligence Interviewer - Server Admin, and records in ApplicationSessionHistory tell you about activities that users have run but are now no longer running. Records in CatiInterviewSession tell you about telephone interviews that are taking place now, and records in CatiInterviewSessionHistory tell you about past interviews.

UNICOM Intelligence Interviewer - Server Admin writes records to the current session tables whenever a user starts what it is that the table relates to, and then updates them while the user is working. When the user stops the task, UNICOM Intelligence Interviewer - Server Admin moves the record to the appropriate session history table. For example, when you use User Administration to add new users and roles to the system, a record is written to ApplicationSession containing your name and the date and time when you started the activity. When you close User Administration, the record moves from ApplicationSession to ApplicationSessionHistory and is updated to show when you stopped using the activity.

If an activity closes due to an error, its record remains in the Session table for at least one hour. This value is defined in the ActiveSessionDataExpiresInHours property in DPM and can be changed. After this time, the record is moved to the appropriate history table the next time the Interviewer Monitoring activity runs. This activity calls a method on the Session Monitoring component that cleans up the tables. If you create your own applications that use these tables, you will need to call this method from your application to perform the same clean-up. The C# code snippet that follows shows how this can be done.

using SPSSMR.Management.Monitoring.DimensionNet.Remoting;
...
// get factory from authenticard agent object
IMRFactory factory = (IMRFactory)agent;
// create RemoteSessionData via factory
object obj = factory.CreateObject("SPSSMR.Management.Monitoring.DimensionNet.Remoting.RemoteSessionData");
RemoteSessionData remoteSessionData = (RemoteSessionData)obj;
// clean application session table
remoteSessionData.Clean(SessionType.ApplicationSession);

The Session Monitoring component that maintains the audit trail obtains information about how it is to run by reading the following properties from DPM:

The number of hours that active session records can remain in a session file. Once this time expires for a record, that record will be moved to the history table the next time someone runs the Interviewer Monitoring activity.

The number of days that CATI session records can remain in a history table. Records that are out of date are deleted from the CatiInterviewerSessionHistory and CatiInterviewSessionHistory tables when the user enters the ConcurrentUsageReport activity. By default, the value is set to 365 days. Use -1 to set an infinite expiry date (that is, records are never deleted).

The number of days that records can remain in a history table. Records that are out of date are deleted from the ApplicationSessionHistory table when the user enters the ConcurrentUsageReport activity. By default, the value is set to 365 days. Use -1 to set an infinite expiry date (that is, records are never deleted).