Configuring OPEX OXI Import

Once you add the OPEX OXI Import input source to a server group, you must configure it to locate OPEX batches and reformat them as Quillix batches. You also have the option to configure the input source to capture any data the OPEX device collected during scanning.

1. In Quillix Process Manager, expand the Server Groups container item in the console tree, if it is not already open.
2. Click on the name of the server group that contains the OPEX OXI Import input source you want to configure.
3. Under Input Sources, click on the name of the OPEX OXI Import input source.
4. Under Input Source Tasks, click Configure This Input Source to open the OPEX OXI Import configuration dialog box.
5. Under OPEX Settings, use the browse button to select a folder where a Quillix Server will find batches created by an OPEX scanner.
6. Optionally, select whether or not to delete the OPEX batches from the source folder after they are acquired by a Quillix Server.
7. Optionally, select whether or not to save a copy of the OPEX batches to a different folder. Use this option only if you intend to store backup copies of the OPEX batches as they existed prior to their import into Quillix. If you select this option, use the associated browse button to specify the folder that will store the copied OPEX files.
8. Under Quillix Settings, select a Quillix batch profile. This batch profile will reformat the OPEX batches according to a particular Quillix batch class and capture workflow process. One OPEX input source instance can be associated with only one Quillix batch profile.
9. Choose a how OPEX documents will be classified by Quillix document type:
   • If you choose the first option, "use OPEX page name as document type," Quillix will look for and use a Quillix document type with the same name as the OPEX "page name" to classify an OPEX document as a Quillix document. Therefore, at run time there must already exist a Quillix document type whose name matches the OPEX page name. For example, if the OPEX page name is "Invoice," then the corresponding Quillix document type name must also be "Invoice." If there are going to be multiple OPEX page names within an OPEX batch, you must create a Quillix document type for each in order to import the entire batch.
   • The second option, "use the default document type," is more simple than the first. During batch import Quillix will classify all OPEX documents using the batch profile’s default document type.
10. Optionally, select whether or not to separate each document that is captured within an OPEX batch into its own Quillix batch.
11. If you intend to capture OPEX data as Quillix document indexes, you must map the appropriate Quillix index field to a known OPEX field. Refer to Optional OPEX Field Mapping to learn how to populate Quillix document indexes with OPEX data.
12. Click OK to save your changes to the input source and to close the OPEX OXI Import configuration dialog box.

Any changes you make to the input source will not take effect until all the Quillix Servers in the server group are stopped and restarted.

Verbose Logging

Select Verbose Logging to record in the Quillix Audit Log detailed information describing this module's processing activity. Without verbose logging enabled, the Quillix OPEX OXI Import module only records error and failure messages in the log. Verbose logging should be turned off during normal system operation.

Related Topics:

• About OPEX OXI Import
• Installing OPEX OXI Import
• Adding OPEX OXI Import to a Server Group
• Optional OPEX Field Mapping