User-based auditing

The Infor Landmark system provides a means to more easily examine and analyze what changes a user might have made or what data the user might have viewed over a specific time period across the entire product. This is accomplished by storing user-based audit log header entries as well as user-based view log entries in the AuditLogEntry business class. The key fields that are stored will enable you to locate specific records if necessary.

The user actions that will be tracked are online user transactions and Infor Spreadsheet Designer web service transactions, and when users view a list or form. That is, batch transactions are not included. Also, selects do not create entries and paging a list will not create entries (only the first access does).

Once the AuditLogEntry business class has been populated, you can view its contents in several ways:

  • The Audit Entries form in the Administration Console. This form shows the list of audit entries. Note that searches with this form may be slow. You can use the Instance Selection field to obtain the keys to single record views. On the Audit Entries List, you can also use the View Source action to redirect to the list that is on the entry or to a form for the record that created the entry (if the record still exists).
  • The Audit Entries Analysis form in the Administration Console. This form shows the ColumnarView list of audit entries. To use this form you must use data replication to replicate to a columnar table. When setting up the replication set for the AuditLogEntry business class, be sure to select the Enable Indicator Replication check box and then select the indicator field to use. For information on columnar tables, see Implementing Columnar Tables.
  • Standard database tools.

For performance reasons, Infor strongly recommends that you regularly purge the records. Only records that have been replicated will be deleted. The recommended schedule would be to run the purge as often as you replicate. You can run the purge by selecting Actions > Purge Archived Data on the Audit Entries form, or by navigating in the Administration Console to Audit Entries > Purge Archived Entries.

To implement user-based auditing, you use several configuration parameters set up in the Configuration Parameters form in the Administration Console. All of these are set in the environment data area (gen).

  • CreateAuditLogEntryRecords: If set to true, the AuditLogEntry business class is created and populated with the key fields for audit log entries that are for online user transactions and Infor Spreadsheet Designer web service transactions. Though you set this parameter only in the environment data area, a separate AuditLogEntry business class is created in each data area.
  • CreateViewLogEntryRecords: If set to true, the AuditLogEntry business class is created and populated with the key fields for audit log entries that are for user-viewed lists and forms. You can also have web services calls create audit log entries by including &_clientType=UI in the URL.. Though you set this parameter only in the environment data area, a separate AuditLogEntry business class is created in each data area.
  • IncludeListFormFieldsViewed: If set to true, the default behavior is changed for the CreateViewLogEntryRecords parameter. The default behavior for that parameter is to not include the list of fields unless the form or list name is not available (which can occur if the form or list is accessed programatically). The IncludeListFormFieldsViewed parameter enables you to include the list of fields whether or not the form or list name was available.
  • IncludeNonListFormFieldsViewed: If set to false, the default behavior is changed for the CreateViewLogEntryRecords parameter. The default behavior for that parameter is to include the list of fields when the form or list name is not available (which can occur if the form or list is accessed programatically). The IncludeNonListFormFieldsViewed parameter enables you to exclude the list of fields whether or not the form or list name was available.

To set up the configuration parameters for user-based auditing:

  1. Log in to the environment data area (gen).
  2. In your Landmark UI, navigate in the Administration Console to Other > System Configuration Parameters > By Residence Category.
  3. On the Configuration Parameter Categories form, in the top list section, filter on and select “AuditLogEntry.”
  4. On the Available Keys By Runtime Component tab, select the entry with the key of "CreateAuditLogEntryRecords," "CreateViewLogEntryRecords," "IncludeListFormFieldsViewed," or "IncludeNonListFormFieldsViewed," depending on which parameter you are setting up. See above for a description of the purpose of each parameter.
  5. Click Create Parameter, specify true or false in the Value field, and click OK.

    To change the value later, select this configuration parameter on the Defined Parameters By Runtime Component tab.