This chapter describes issues associated with Oracle WebCenter Enterprise Capture. It includes the following topics:
Note:
Ensure that the most recent patches are applied. You can download patches from My Oracle Support (support.oracle.com).This section describes Client issues. It includes the following topics:
Section 7.1.1, "Certain Client Error Messages Display in Server Language"
Section 7.1.2, "User having only client profile access unable to view client profiles"
Section 7.1.3, "Error encountered if F9 key was pressed when using an Index-Only client profile"
Section 7.1.5, "Error 401 indicating unauthorized access was encountered in the Capture client"
Section 7.1.6, "Unable to display scanner configuration dialog with some scanner drivers"
Section 7.1.7, "Scan performed in duplex mode when simplex mode was specified"
Section 7.1.8, "Issue with document separation when Prompt User option was used"
An issue was discovered in which some error messages in the client display in the server language rather than the browser language.
An issue was discovered in which a user having only client profile access was unable to view any client profiles in the Capture client. To workaround this issue, add the user to the workspace as either a Workspace Viewer or Workspace Manager.
When using an Index-Only client profile, pressing the F9 key produced an error and numerous null batches.
An issue was discovered with item count displaying incorrectly for a batch in the Capture client after deleting items from the batch, releasing the batch, and refreshing the batch list.
An issue was discovered in which the error 401 indicating unauthorized access was encountered in the Capture client when a valid WLS user, not assigned the CaptureUser role tried to log in into the Capture client.
An issue was discovered in the Capture client with the scanner configuration dialog not being displayed for some of the scanner drivers.
An issue was discovered in the Capture client with the scanner scanning in duplex mode after selecting to scan in simplex mode from the scanner settings dialog.
A client profile issue was discovered in which the document separation did not occur when Prompt User option was selected in the Document Creation Option field unless the user scanning the batch in the client specified to detect separator pages. To work around this issue, in the user prompt dialog (Document Creation Options window), select the "Identify separator if bytes scanned is less than Bytes value" option.
An issue was discovered in which the date field used in document titles was not correctly formatted when committing to Content Server.
This section describes Import Processor issues. It includes the following topics:
Section 7.2.1, "Import Processor unable to import BASE64 encoded email"
Section 7.2.3, "Large TIFF image file not imported by the Import Processor"
Section 7.2.4, "Import failed and exception message encountered for some email messages"
An issue was discovered in which the import processor that was set to monitor an email inbox and import every email was unable to import a BASE64 encoded email.
An issue was discovered when an email attachment containing the / character in the filename was processed by the Import Processor. The Import Processor job was unable to process any further emails until that email was removed from the email folder. To work around this issue, use an email client to forward the email, which sometimes corrects the issue, or save the attachment with a different file name, then forward or recompose the email using the attachment with the new file name.
An issue was discovered when trying to import a large TIFF image file using the Import Processor. To work around this issue, import the TIFF image file using the Capture client.
An issue was discovered in which the Import Processor configured to import from an Email Source failed to import some of the email messages during processing and logged the exception message "Error saving message body" in the server log file. In some cases, forwarding the email and reprocessing it may be a work around for this issue.
There are no known issues at this time.
There are no known issues at this time.
This section describes Commit Processor issues. It includes the following topics:
Section 7.5.1, "Delimiters not written to Input Agent file when first mapped indexes are empty"
Section 7.5.2, "All mappings updated when modifying a row in Content Attribute Mappings"
An issue was discovered in which the delimiters were not written to the Input Agent file if no values were specified for the first mapped fields when configuring the WebCenter Content Imaging commit driver to use the Input Agent as the commit method.
A Content commit profile configuration issue was discovered in which editing a row in the Content Attribute Mappings table on the Check-In tab modified all the rows with the same latest values. To work around this issue, delete the old mapping row instead of editing it and add a new one.
This section describes general issues. It includes the following topic:
An issue was discovered in which the error 401 indicating unauthorized access was encountered after logging into the Capture applications. To work around this issue, restart the Capture managed server.
There are no known issues at this time.