You can customize the change tracking functionality one of two ways:

You can create a plug-in class override and method within that overriding class and specify the overriding class and method as the pluginClass and pluginMethod for the target class, using the appropriate property setting in the lcs.plugins.properties file.

It is assumed that if you are overriding the plug-in class and method that you are doing so for a specific business need or that the custom plug-in handles the complete implementation of the given event, including the creation of the ChangeAuditEvent and ChangeAuditEventDetails.

You can use this approach if your business needs require you to capture event changes that are not currently supported out-of-the-box or to capture event changes for objects for which change tracking is not currently supported. In these cases, you can append similar entries to the changeTracking.xml file in order to gain additional flexibility with the customization or, if you do not require greater customization flexibility, you can have the system process these entries in the custom plug-in.

You can create a processor class override and specify this overriding processor using the <processor> element in the changeTracking.xml file.

When using a custom processor class, you must ensure that the custom processor class either extends the DefaultChangeAuditProcessor class or implements the ChangeAuditProcessor interface. If the custom processor class does not extend the DefaultChangeAuditProcessor class, then you must use the ChangeAuditProcessor class to implement all events for the given object.