Changes

The following table outlines all logging mechanisms within the SmartSimple Platform. Logs can be viewed through the regular platform interface, by system administrators, while a subset of these logs may also be made available to non-administrator users as well. Some logs may also be made available to export through the use of Report Builder feature, as indicated by the Available to Export column. Certain logs are feature, or configuration dependent, and as such will not automatically be captured unless explicitly enabled, as indicated by the Requires Configuration to Enable column.

{| borderclass="1wikitable"! align="center" | Log Type || align="center" !| Log || align="center" !| Description !|| align="center" | Available in Interface || align="center" Requires Configuration to Enable!| Available in Reportingto Export

| System |Access| Login History |Access Modification| Tracks login and logout date and time |Changes to a user's access. Captures the following actions:* activation/deactivation of user.* change to user role.* password resets.| No | || Yes

| System |Access| Locked Users |Failed Login| Tracks locked users |Failed authentication attempts.| Yes | || No

| System |Access| Locked User History |Login Session| Tracks all locked users by month |Successful logins, and user sessions. Captures the following attributes:* session start time.* session end time.* user's originating IP address.* user's browser agent.| Yes | || NoYes

| System |Access| Message Queue |Primary Authentication Controller Login| All messages generated by all workflow requests across all applications| User logins that originate from the Primary Authentication Controller feature, which allows users to authenticate between SmartSimple instances. The system will automatically capture these logs as long as the Primary Authentication Controller is configured, and used to authenticate between instances. || Yes || NoYes

| System |Access| Contacts and Companies |User Activity History| Logs all deleted contacts and companies. Records can be retrieved by System Administrator| Each individual page request made during a user's active session. || Yes || No

|| System Configuration|| Custom Field Setting Deletion|| Tracks history Deletion of changes made to custom field settingsCustom fields. Feature must be enabled for The previous states of each custom field. This function is not available for standard are captured to allow you to restore the field outside the UTAif needed. || Yes || No

|| System Configuration|| Deleted Custom Fields Field Modification|| Logs all deleted Changes made to custom fieldsfield configurations, from field formatting, to access permissions. Fields can be retrieved by System AdministratorThe previous states of each field are captured to allow you to restore the field if needed. || Yes || No

|| System Configuration|| Field Value General System Modification|| Tracking change history of Changes made to various system areas. Captures changes to fields’ valuesthe following areas:* Reports.* Workflows. || Yes || No

|| System Configuration|| Geocoding Security Matrix Modification|| User requests Changes made to security matrix constructs that define the access control permission of user roles to retrieve Latitude UTA records, companies, and longitude for company or contactusers. || No || No

| UTA |Error| Reader Log |System Error| Tracking viewers for level 1| System errors occurring in the platform, 2 as a result of the configuration and 3 objects. Feature must be enabled in UTAusage of your instance. || Yes || No

| UTA |Operational| Status Change |API Usage - SmartConnect RESTful| Tracks status changes for level 1, 2 and 3 objects. Feature must be enabled in the status field at | API calls made to the required levelSmartConnect RESTful API receiver. || Yes || Yes

| UTA |Operational| Record Lock |API Usage - SOAP Web Service| Tracks locked record history for level 1, 2 and 3 objects| API calls made to the SOAP Web Service API receiver. Feature must be enabled in UTA for the required level || No || No

| UTA |Operational| Package | Integration Usage - Data Exchange || Tracks Activity related to the transfer use of packages from one instance of SmartSimple the Data Exchange feature, which is used to Anotherexchange records between instances. || Yes || No

| API Requests |Operational| Request History |Integration Usage - E-Signature| Tracks all Pandora API requests including | Activity related to the developer IDuse of E-Signature integration feature, Request function and the date/time of the request which is used to send E-Signing requests to supported partner systems.|| No || No

| External WebPages |Operational| Access History |Message Queue| History of access to all external pages via | Email messages generated and sent from the Internetsystem. These include signup pages (Applicant and standard) and external reporting pages || Yes || No

| OS Level |Operational| Apache Logs |Privay and Security Policy Agreement| A set | User acceptance of Apache logs is maintained. This link provides further details: http://httpd.apache.org/docs/1.3/logssystem privacy and security policies.html || No * || No *Yes

| OS Level |Operational| SSH Log |Record Deletion| SSH Access log is maintained| Deletions of records, from UTA records, to companies, to users.|| || |-|| Operational|| Record Modification|| Changes made to records, from UTA records, to companies, to users. The track changes option must be enabled for each individual field that you wish to track the change history of. This link provides further detailsCaptures changes to the following attributes: http://www* standard field values, including status.* custom field values.|| Yes|| Yes|-|| Operational|| Record View|| Tracks each time UTA records are opened and accessed by users.sshThe reader log option must be enabled within each UTA, and each UTA record level in order to track this.com/support/documentation/online/ssh/adminguide32/log_messages|| Yes|| Yes|-|| Operational|| Workflow Process|| Automated Workflow tasks that have been triggered and run against records.html || No * || No *