Simple configuration and description of filenet Auditing

The auditing function of filenet can audit operations on ce classes (events ). So what is the business need for this kind of auditing? For example, one of the important roles of the Information Department of some enterprises is to informatize the enterprise information. The process of informatization can be divided into two categories. The initial stage is electronic documentation, the advanced stage is archive. E-document is based on a kind of preliminary information of departments or leaders. Some of the requirements or application systems formed on this basis are blind, and the key to clearing this blindness is to fully obtain the in-depth understanding and recognition of the work of the Information Department from the superiors, on the other hand, you need to consider the system in depth for improvement. The latter may directly affect the former, and one of the implementation methods of the latter is audit. The following describes how to configure and view the filenet auditing function.

 

Enable auditing at the ObjectStore level

Specify the event (events) to be audited on the class that requires Auditing)

 

The above configuration can also be completed through the API, here only a brief description of the above configuration. We can use the ObjectStore auditlevel attribute to determine whether it can be audited. If this attribute returns 1, that is, yes, and 0 is returned, no. You can select the event to be audited when setting for a certain type of audit. You can also select the successful or failed action to audit the event. After an event occurs, the corresponding creation time and event source information are recorded in the audit log, which is an event table.

 

Filenet auditing contains a wide range of events, for example:

Cancelcheckoutevent

Changeclassevent

Changestateevent

Checkinevent

Checkoutevent

Classifycompleteevent

Creationevent

Deletionevent

Demoteversionevent

Promoteversionevent

Fileevent

Getcontentevent

Getobjectevent

......

......

 

In addition, we can view the audit history (the API can do the same) in the attributes of an instance, and display the information of the getcontentevent (this event will be triggered when the document is downloaded or checked out ).

 

The above statistics occur on the document, and its audit history corresponds to the corresponding version of the current instance. If the above instance version is upgraded, the history only exists in the corresponding version.

 

This article briefly introduces the necessity of the auditing function from the one hand (the recognition of leaders in the initial stage of informatization and the improvement of the system itself, the process for configuring auditing from the FEM and the method for querying audit history are further described. It is also pointed out that the above operations can be further implemented from the API perspective. That is, filenet fully considers the use of audit from the Administrator and developer perspectives.