Using kofax reporting with custom modules – Kofax Capture User Manual

Page 11

Kofax Capture

Kofax Product Support for Kofax Reporting

▪ Registration or unregistration is completed via

RegAscSc

▪ Kofax Capture records the custom module add or remove action when:

▪ The add or remove event is completed in the Custom Module Manager window in the

Administration module

▪ Registration or unregistration is completed via

RegAscEx

RegAscCM

▪ Kofax Capture records the workflow agent add or remove action when:

▪ The add or remove event is completed in the Workflow Agent Manager window in the

Administration module

▪ Registration or unregistration is completed via

RegAscEx

RegAscCM

▪ Kofax Capture does not record any “version_info” for the add or edit script actions for the

following types
▪ Field
▪ Folder
▪ Document
▪ Recognition profile

Note that the command line utilities that do not require a user to login will not have data for

user_logon_key

Using Kofax Reporting with Custom Modules

There are several factors that affect the integration of Kofax Reporting with custom modules.

Custom modules that were written using the older XML-based custom module library report

only batch open and close actions. This limits the amount of information available to Kofax

Reporting.

If the newer DBLiteOpt API is used, Kofax Capture automatically saves reporting data for

the module. However, a custom module can optionally specify that Kofax Capture should

not create reporting data. In this case, the custom module is responsible for reporting all

operations.

Note This reporting data is distinct from user tracking data, which is not automatically

recorded. The recording of user tracking data is up to the custom module.