Troubleshooting

Refer to the issues below for assistance in troubleshooting the Document Design Accelerator. For issues related to the Semantik AI Engine, see Troubleshooting (Semantik AI Engine).

Issue Possible Root Cause Solution

An error occurs when dragging a file into the Create Document Type from Sample panel.

Semantik AI Engine is not installed and running.

Contact your administrator to install and/or start the Semantik AI Engine service.

The Create Document Type from Sample panel is not visible.

Your Transact instance is running a version prior to 2022.1.00 or Transact 2022.1.00 or later is running, however the display_key_value_accelerator_sample_panel property has not been enabled and Transact has not been restarted.

Contact your administrator and ask them to follow Hide or display Create Document Type from Sample (Document Design Accelerator) panel.

Document Design Accelerator returns few or no index fields.

An unpopulated form was dragged into the Create New Document Type From Sample panel.

Confirm that the sample used in Create a Document Type from Sample is a populated form. The Document Design Accelerator will not create index fields or extraction rules unless it detects both a key and a value pair. Blank forms are likely to contain only keys and will not result in the automatic creation of index fields and extraction rules.

Documents of the document type created using the Document Design Accelerator are not being classified correctly.

The document type was not trained for classification.

Train the document for classification.

Document Design Accelerator may not create a table extraction rule that joins tables that span across pages. Or, it may create several table extraction rules when fewer are expected.

Column widths for similar tables may be inconsistent.

Adjoining table logic:

  1. All pages are submitted sequentially to Semantik AI Engine.

  2. Semantik AI Engine returns a list of tables along with coordinate information for tables, headers, and columns.

    There is no distinction between the number of tables in the list.

  3. The same-table detection logic iterates through each table and compares attributes to determine if the tables should be joined:

    • Count of columns

    • Width of columns

To adjust the option that controls comparison logic for spanning tables across pages, edit the sre_acceptable_column_width_difference option in the application.properties file. A 30 pixels variation in column size matching is set by default.