Overview
For Cora AP Capture, the configuration includes defining the saga steps and configuring a yaml file each for all the saga steps like extraction, enrichment, and validation in a workspace.
The configuration of each workspace is defined as a ConfigSet in the Administration site. The basic configuration is available out-of-the-box (Extraction_Configuration), however, a user with access to the Administration site and rights to modify configuration can update the configuration per requirement.
Create a ConfigSet
- In the Administration site, go to Administration>Global Settings>ConfigSets.
- Copy the Extraction_Configuration, to create a new ConfigSet for a workspace.
- Edit the new ConfigSet to make changes.
The window to edit configuration properties opens up in a new tab in your browser window.
Each yaml file is a configuration file for different steps. - Click a yaml file to open and update the parameters per requirement.
Following is the list of configuration files defined in a ConfigSet:
| Configuration file | Description |
|---|---|
| additional-charges.yaml
(applicable only for invoice processing) |
Configures properties for any additional charges to be included in the invoice. |
| apflow-mapping.yaml | Configures the fields to translate the extracted and stored data (from JSON) to an XML or a JSON file. |
| classification.yaml | Configures the classification model based on which the documents are classified. |
| classification-results.yaml | Configures the extraction model that will be used for extraction of data from the document(s). |
| culture-resolution.yaml | Configures the language and style for the data in the system. |
| extraction-model.yaml | Configures the system schema, the fields that will be translated to JSON from the data extracted by the DocIntel. |
| eyeball-client-configuration.yaml | Configures which fields will be visible in the eyeball page in the UI and how. |
| eyeballing-decision.yaml | Configures the rules, like confidence percentage, on fulfilment of which the system will continue to the eyeball step.
For example, if the configure percentage is 70 then the system doesn’t need eyeballing. If percentage is less than 70 then the system performs the eyeball. |
| invoice-enrichment.yaml | Configures the data source for enrichment, and rules that determine which data is taken for enrichment of extracted data. |
| invoiceLineItem-invoice-enrichment.yaml | Configures the enrichment rules for line items. |
| lineItem-validation.yaml | Configures the validation rules for line items. |
| saga.yaml | Configures the order steps of the Cora AP Capture process. You can define the order in which you want to execute the steps and the steps that you want to skip. |
| side-car.yaml | Configures the attributes of the metadata of files from which data is picked. |
| split-configuration.yaml | Configures the parameters based on which a document is split in multiple documents. |
| tables-data-model.yaml | Configures the mapping of fields in the master data to the fields in the JSON.
Also contains the stored procedure to calculate the operational address code. |
| tenant-workspace-configuration.yaml | Configures the workspaces for each document type. This yaml defines the connection to the master data, workspace port and other workspace related parameters. |
| validation.yaml | Configures the validation rules. |
Connect a ConfigSet to a workspace
- In the Administration site, go to Administration>Lookup Table>IDE Saga.
- For tlbTenants, create a new record with a specific name.
- For tlbTenantWorkspaces, create a new record and add the following details:
- fldSlug: The name of the workspace.
- fldConfigSetId: The ID of the ConfigSet created for the specific workspace. Copy the ID from the ConfigSet (Administration>Global Settings>ConfigSets), and paste here.
