|
Preprocessor Parameter |
Description |
|---|---|
|
Preprocess |
If a file is in a format that cannot be processed by Statement Composition, an outside program preprocessor can alter the file so it can be processed. When the Preprocess check box is selected, the specified preprocessor is executed on every file residing in the Default Directory and Default File Name fields. Enable this check box to run the preprocessor executable prior to processing the Statement Composition data file. |
|
Preprocessor |
Select this button to access a dialog box that allows you to specify the location of the preprocessor executable (Preprocessor Location), as well as other required parameters (Preprocessor Parameters). |
|
Processor Location |
Indicates the full path to the preprocessor executable. You may type this path manually or click Browse and navigate to the file. Note:
This field is limited to 255 characters. |
|
Preprocessor Parameters |
Because each preprocessor used is unique to its application for a Statement Composition data file, the values supplied for the Preprocessor Parameters will vary depending on your installation. These values will be communicated to the system administrator when the system is installed. Two of the most common parameters are input file and output file. For most preprocessor, the parameter input field will contain the characters "%I %O" followed by an application-specific command line. Note:
This field is limited to 128 characters.
CAUTION:
The parameters must be listed in the following order: %I %O. If the order of the parameters is reversed (%O %I), all data will be removed from the data file. |
|
Successful Return Value |
Enter the expected number (or range of numbers, using < or >) that the preprocessor returns after a successful process. If the preprocessor does not return a successful value, the file is not processed. This value is dependent on the type of preprocessor used, and will vary depending on the installation. This value will be communicated to the system administrator when the system is installed. Note:
In Document Import Processing, this field is limited to nine characters. |
|
Add Documents to Workflow |
Note:
To use this option you must be properly licensed for Workflow. The processed documents are placed into any workflow associated with the Document Type with which the documents are associated. Once the Add Documents to Workflow option is selected, you can:
Note:
Documents can only be added to Unity Life Cycles from the Core-based OnBase Client interface. Note:
When using the Core-based OnBase Client interface, if one or more documents are not successfully added to Workflow, the batch will be added to the Committed queue. When using the classic OnBase Client interface, if one or more documents are not successfully added to Workflow, the batch will be added to the Incomplete Commit queue. Tip:
When using the Core-based OnBase Client interface, it is recommended that you always select On Commit. CAUTION:
When using the Core-based OnBase Client interface, it is required that you select On Commit if your Workflow is configured to perform any System Work. |
|
Note:
If you enter a path that does not exist (i.e., a folder not already created), it will automatically be created during the first processing. |
|
|
Select the Create Unique Subdirectories check box when each data file that is being processed has the same name and each file needs to be backed up. By default, if a process to be run uses a text file that will have the same name (but different content) each time, each new backup of the text file will overwrite the old one. Select this check box to create a unique subdirectory within the specified backup directory for each text file. The directory will be created in the following format, based on the date and time of the batch processing: “06_15_2007_14_22_45.” This option will also function with FTP backups, if applicable. |