Help > Setting up document capture > Importing solutions from Capture Components Administration

Importing solutions from Capture Components Administration

If you need to use the ReadSoft Capture Components activities, you must configure how you want them to work in XBOUND. Part of that process is to import a solution from the Capture Components Administration module. (ClosedMore information.)

Solutions contain document specifications, which are connected with XBOUND document types, either by a default configuration or using your own settings. The connection between document specifications and XBOUND document types determines (1) the XBOUND document type that is assigned during Classification, and (2) which fields will be created in those documents when you process them.

Use the Import Solution activity to do this.

Note: Before you configure any process step, you must first:

Please refer to XBOUND Help for instructions.

Important
  • Capture Components field names are currently case sensitive, whereas XBOUND field names are not. This means that importing your solution to XBOUND can result in two fields with the same name but different capitalization (for example Accountnumber1 and AccountNumber1). This causes errors in XBOUND processes. You must ensure that the field names in the solution have exactly the same capitalization as corresponding XBOUND fields (if any).

  • Ensure that field names in the solution do not begin with spaces.

Global, client, and process levels

You can define parameter sets—and thus import solutions—on the global, client, and process levels:

For important instructions about importing solutions on the global and client levels, see step 8 below.

To import and configure solutions

  1. Using the XBOUND Process Designer:

  2. In the Parameter sets dialog, drag Import solution to the right pane and name it.

    If you do not see Import solution, it is likely because xBoundActDOXImport.dll was not added to the global parameter set after installation as described in XBOUND Installation Guide. In that case, do this first:

    1. In the Parameter sets dialog, right-click under Activities and select New activity. The New Activity dialog is displayed.

    2. Click in the Path to DLL box and navigate to and double-click xBoundActDOXImport.dll. This is normally located in C:\Program Files\ReadSoft\xbound.

  3. In the right pane, click the button in the Parameter sets column.

    The Import Solution settings are displayed in the Parameter set dialog.

  4. Click the Import and configure solution button. The Import Capture Components solution dialog is displayed.

  5. In the Deployed solutions list, select a solution from the list of those that are available.

  6. In the Classification field name box, specify the name of a field where classification results are to be saved.

  7. Click Import solution.

    If you are importing a solution on the process level, XBOUND document types are created automatically, and a message is displayed to tell you the results.

    If you are importing a solution on the global or client level, Closedthese additional steps are needed.

    1. Open the global or client Parameter sets dialog (see step 1 above), locate the solution parameter set you are working with, and click the button in the Parameter sets column for this solution parameter set.

    2. At the bottom of the Import solution settings, click Export and save the parameter set as an XML file. Click OK and then Close.

    3. Right-click a process, select Parameter sets, locate the solution parameter set you are working with, and click the button in the Parameter sets column for this solution parameter set.

    4. At the bottom of the Import solution settings, click Import and browse to the XML file you created above. Click OK and then Close.

    5. Open the parameter set at the process level and click OK. All documents, including fields, are created.

    6. Optional: Delete the parameter set from the process level.

    7. Repeat this procedure every time you change the mapping or import a new or altered solution, resulting in the new XBOUND documents or fields.

  8. Repeat steps 1–8 as needed for additional solutions.

  9. Click Close.

  10. Next:

    • If you click OK now, a new XBOUND document type is automatically created from each top-level document specification that was included in the Capture Components solution. Each resulting XBOUND document will contain all of the fields that each top-level document specification contained, as well as all of the fields that each of its sub-documents contained. ClosedExample:

      As mentioned above, field import is currently case sensitive, whereas XBOUND is not.

    • Customize the connections between the imported solution and the XBOUND document types.

Note: You can import a solution two or more times (for example after editing and re-deploying the solution in Capture Components Administration). However, between imports you must save and close the process. The status bar in the bottom left corner of the XBOUND window tells you whether the process is checked out.