Using the WebCenter Content: Imaging Input Agent Commit Profile with Enterprise Capture Results in the Creation of Text Files In Incorrect Format When the First Field Is Not Populated
(Doc ID 1958723.1)
Last updated on SEPTEMBER 27, 2022
Applies to:Oracle WebCenter Enterprise Capture - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11g to 12c]
Information in this document applies to any platform.
After configuring an Imaging Input Agent commit profile for a generic Capture Scan and Index application, some fields are not required to be populated, so the user may or may not enter a value. When the Input Agent commit creates the text file, it if failing to leave a blank space for these values. This then causes the import to fail because the text file is in the wrong format. Delimiters are not written to Input Agent file when the first mapped indexes are empty.
Configure the WebCenter Content Imaging commit driver to use the Input Agent as the Commit Method. Choose an Imaging Input Definition that has at least 2 fields available for mapping. Map the first 2 fields to Capture fields. Create a batch in the Client but don't assign values to these fields, then commit the batch to the Imaging commit profile. You'll see only the file name is written to the input agent text file and there are no delimiters for fields 1 and 2.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document