OCRN-602 Attachments: Import of attachments not only by GUID but also by the separator “_”

In the database, table Profile, column AttachmentFilenameGuidFinishCharacter, it is now possible to set the separator for the identifier by which the document and attachments are linked (INT value, 0 = 36 characters (standard GUID), 95 = “_” character as separator = identifier is from configured start position to separator).

 

OCRN-604 Order workspaces alphabetically

In table OcrParams, it is now possible to set the parameter WorkspaceAlphabetOrder. 1 = workspaces in the list are ordered alphabetically.

 

OCRN-610 Export "Source file NG"

In the admin module, it is possible to set a new export (new generation) – Source file NG:

• ExportData: if there is a value “rename”, the value of the attribute specified in ExportData1 will be used as a file name.
• ExportData1: DevIdAttribute of the attribute. Value of this attribute will be used as a file name. Attention! This value cannot be an absolute path, but you can use it for a relative path. (Example: Attribute value: \subfolder\name.pdf, export path C:\export Result: C:\export\subfolder\name.pdf).
• ExportData2: if the full path of a folder is configured, the file will be saved into this folder instead of the folder specified for the profile.

 

OCRN-615 Export CustomXML: New tag for exporting attachments

In the CustomXML export, it is now possible to export attachments for the document. In the template for header, you can add the tag {{Attachments}}. For every attachment, this tag will be replaced by the content of the template for attachments (filename of the template for attachments has to be configured in ExportData6 – it is now possible only in the database, table ProfileExport). In this template tags {{FileName}} (exported filename) and {{OriginalFileName}} (original input filename) can be used.

 

OCRN-532 Admin: option to delete all documents in the state “Waiting for user check”

In the admin module, profiles of the workspace, you can now delete all documents in the state “Waiting for the user check” in this profile – option will be displayed after right-clicking the profile.

 

OCRN-611 Export CustomXML: Tag "FileName" now uses the new name of the file in case of renaming; new tag “OriginalFileName”

When exporting with CustomXML export, there could be a mismatch between filename in XML and real filename. Now you can use two tags in the CustomXML: {{FileName}} (name of the exported file) and {{OriginalFileName}} (original name of the input file).

 

OCRN-618 Export CustomXML: new tag “CustomXml” is replaced with the content of the “CustomXml” column from the table “Document” for the exported document

In the template for the header, you can not use the tag {{CustomXml}}. It will be replaced by the content of the CustomXml column from the Document table. This is useful if the export (of the part of it) needs to be dynamic. You can set it before CustomXml export by stored procedure and then use it in CustomXml.

 

OCRN-606 Line items: in validation XML there is not the second value of the fixed set (id), it is also missing in export

Item attribute of the type “fixed set” has two values, Value and ValueId. Id was added to validation XML as an element ValueId. In the CustomXML export, you can use it in the template for items by using the tag {{DevIdAttribute_ValueId}}.

 

OCRN-613 Export "Konica minolta XML": update file naming to a similar principle as CustomXML

In the element OriginalFileName, the name of the original input file is exported, element page_images contains the path to the exported file (it can differ from the original file name because of the renaming).

 

OCRN-619 Event OnDocumentExportsStart

For each profile, it is now possible to configure the procedure, which will be executed before running the exports for the profile. You can configure this procedure in the table Profile, column OnDocumentExportsFinish (name of the stored procedure from the OCR database).

 

OCRN-624 Rename the stored procedure ProcessDocument_Custom to _OnProcessDocumentStart

Custom stored procedure executed before the document processing was renamed.

 

OCRN-625 Event OnProcessDocumentFinish

Event (stored procedure) executed after finishing the document processing in OCR (you can edit the procedure _ OnProcessDocumentFinish to execute custom code).

 

OCRN-626 Event _OnDailyDatabaseMaintenance

New event (stored procedure) created, it is executed during the daily database maintenance (you can add custom code to this procedure).

 

OCRN-637 Line items: Possibility to add a new row above/below selected line added to line menu (it was only in the button menu)

 

OCRN-644 Line items: Possibility to set the value as valid with an empty value

In the admin module, you can now switch the “Empty value is valid” for the item attributes (empty value in the attribute is then allowed in validation).

 

OCRN-617 Client: translate client to Lithuanian

The client application Lithuanian localization was added.

 

OCRN-645 Client: dynamic width of the attribute name (the whole name is not displayed if it’s too long) + remembering of the selected width

In the client, when resizing the attribute area, attribute name was not resized. Now, when resizing attribute area, the attribute name is resized dynamically as well.  The attribute area width is saved for current workspace and user.

 

OCRN-647 Attribute modification "TitleCase"

New modification alters the extracted text. Each word is extracted with the uppercase first letter and the rest in lowercase.

 

OCRN-647 Attribute modification "UpperCase" and "LowerCase"

New modifications added, they transform the extracted text to UpperCase/LowerCase.  

 

OCRN-653 Export CustomXML: tags for the header can be used in the template for items

In CustomXML export, it is now possible to use the header attributes in the template for items.   

 

OCRN-655 Export CustomXML: possibility to set the encoding for the exported file

You can set the encoding for the exported file in the database, table ProfileExport, column ExportData7. You can set one of the values: ANSI, Unicode, Big-endian Unicode, UTF-7, UTF-8. The default is (and always was) UTF-8.

 

OCRN-179 Admin: error when saving attribute modification for the attribute, which is not saved

Fixed.

 

OCRN-257 Line items: if more lines are extracted into one attribute, the ordering of the text is mixed (invalid)

It is a general problem with extracting values by ABBYY engine. Default is ABBYY ordering (in some cases causes invalid ordering). This can be switched off in the table OcrParams, value UseABBYYWordOrderInRegions = 0. With this configuration, the ordering is recalculated and should be ok.

 

OCRN-630 Client: focus on the first attribute does not work if the first attribute is set as hidden

Fixed.

 

OCRN-632 Client: when there is a lot of line items (100+), they are not displayed correctly and switching between values (even general attributes) is slow

Optimized.

 

OCRN-633 Client: list of values of the set attribute is still visible if the attribute is set as hidden

Fixed.

 

OCRN-649 Client: Error when deleting attribute learned history

In some cases, the database error occurred when the user tried to delete attribute learned history – fixed.