Help > Activities > Knowledge Processing activity

Knowledge Processing activity

This activity is used for online "learning" of classification and/or interpretation. Based on user input in Verification (RCF activity) and/or Inspection, document classes and interpretation fields handled by the Classification and Interpretation activities are learned automatically.

During Knowledge Processing, the Knowledge Processing database is updated with layout data points (LDPs). (For more information, see How and when are layout data points added?)

If you need to add this activity to the XBOUND Process Designer, the file to add is xBoundActivityKSFeedback.dll. (For instructions, see the XBOUND Help topic Adding an activity to the Process Designer.)

Note: This activity must be assigned to an Activities Service in order to run. (For instructions, see the XBOUND Help topic Assigning activities to the Activities Service.)

These settings are available when configuring the Knowledge Processing activity.

Parameter Set

Solutions imported from Capture Components Administration. In the drop-down list, solutions imported on the global and client levels are followed by [Global] and [Client] respectively. Solutions imported on the process level are displayed without an extension.

Select the parameter set (solution) you want to use for this activity.

Important: The Knowledge Processing activity must use the same parameter set as the preceding activities in the same process.

The other functions of the Knowledge Processing activity are controlled by the classifiers and/or fields that were included in the imported solution.

As always, the Parameter Set dialog contains Import and Export buttons for importing or exporting settings from this activity. However, since this activity contains no settings, the buttons have no reasonable application.

ReadSoft Capture Components activities: Overview

Knowledge Processing: Overview

Knowledge Processing Explorer

Creating an XBOUND process that uses Knowledge Processing

Finding and deactivating LDPs that are corrupt or learned the wrong document class

Changing the document class

Troubleshooting: Connection with the Knowledge Processing Service is lost

Troubleshooting: Knowledge Processing mixes up two documents