CaptureBites MetaServer Version History

Here you will find all MetaServer release notes, including details of added or adjusted features.

You can always download the latest version of MetaServer on the MetaServer Product Page.

Version 3.0(17) | 2019-08-14

NEW: EXPORT TO SHAREPOINT: With the MetaServer Export to SharePoint action, you can export documents to SharePoint on premise or SharePoint Online.

You can construct the folder structure and file name using fixed elements and variables or metadata fields.

Select a library and content type and map variables or metadata fields with its columns.

The export connector makes use of SharePoint’s versioning feature and when a document with the same name is exported a new version of the document will be created.

FIX: If C:\META-DEMO did not exist and you opened an Extract action, opened an Extract Text rule and pressed OK, you got an error “System.Exception: Trying to delete a file with a very short path:”.

Version 3.0(16) | 2019-08-12

NEW: EXPORT TO ALFRESCO: With the MetaServer Export to Alfresco action, you can export documents to the Alfresco Community Edition or the Alfresco Content Services Enterprise Edition.

You can construct the folder structure and file name using fixed elements and variables or metadata fields.

Select a custom document type and map variables or metadata fields with its properties.

The export connector makes use of Alfresco’s versioning feature so, when a document with the same name is exported, a new version of the document will be created.

NEW: LOAD BALANCING OPTION: If you watch the same folder(s) with several MetaServers, you need to keep your Import queue low so the documents are evenly imported among all servers. If lots of documents end up in in Validation, all servers become idle. To avoid this, you can now enable the new Load Balancing option in the server tab and set the load balancing limit which does not take documents in validation in consideration. The import limit is an absolute limit including documents in validation.

In summary, the Load Balancing option is all about keeping all servers busy by ignoring documents in validation.

Both limits consider imported documents” before separation”.  So a document that is separated in 10 documents only counts as one.

For example:
– Import limit = 20
– Load balancing limit = 5

6 document sets (a document set is a document before separation) are imported and each document set is separated in 10 documents.

8 documents are processed automatically and 2 stay in validation. As soon as all 8 automatically processed documents leave the system and the document set only has documents in validation, that document set is not counted anymore for the load balancing limit.

If all 6 imported documents only have documents, MetaServer can pull in 5 other document sets because the 6 in validation don’t count anymore.

The total number of document sets in the system will be 6+5 = 11, 5 are actively processed and 6 are sitting idle in validation.

If the number of document sets with only documents in validation exceeds 20, the server will pause until documents are validated and some document sets completely disappear from the system.

Version 3.0(15) | 2019-07-25

NEW: TASK SCHEDULER MODULE. This is a new module to run repetitive tasks automatically triggered by one or more timers.

The functionality of the new Tasks feature is fully documented in the MetaServer Online Help.

The Task Scheduler is a separate module in the price list with the following product code:
CB-META-TASK: MetaServer Task Scheduler

Currently there are two main use cases:
1) Syncing a MetaServer database with an external database such as Ms SQL table and cleaning up inconsistent values with replace rules and dedupe records.
2) The automatic deletion of outdated processed document backup files or any other backup files.

The first use case is for the automatic synchronization of any type of database table (MS SQL, ODBC, MetaServer) with a MetaServer database. The sync action allows to sync all columns of the source table or only a selection of columns.

In the process, one or more columns of the resulting MetaServer database can be cleaned up, using following cleanup rules:

– Replace: E.g. Replace all “Inc.” and “Incorporated” at the end of all company names. Or replace all periods “.” with nothing in all VAT IDs.
– Remove Spaces: E.g. Remove all spaces between digits in IBAN numbers and TAX IDs.
– Sort by Column rules: E.g. Sort a table by company name.
– Delete Records by Value: E.g. Delete all records where the field type = TEST or Delete all records where the field type = { No Value }
– Delete Duplicate Records: E.g. Only keep records with unique Client IDs.
– When the source database of a MetaServer sync task is not available, the task is skipped until the next scheduled trigger and an email alert is sent if email alerts are enabled for that task.

To check the result of your database sync and cleanup task, you can use the Run Now function and after the task has finished, open your database directly from the Task ribbon. Press the Open Database button to select a database from a list of all MetaServer databases on your system. The button’s drop down shows recently opened databases for quick access.

The MetaServer database will open with the Windows program associated with *.csv files. If there is no associated program defined for *.csv files in Windows, the “How do you want to open this file” Windows dialog will be displayed. Using that dialog, you can associate a default program with the *.csv file type. If you want to change the default program associated with *.csv files, right-click such file in Windows File Explorer and select Open with… / Choose another App / … Select your preferred *.csv Application and select the [ X ] Always use this app to open .csv files.



Version 3.0(14) | 2019-06-22

– NEW: CHANGE TO THE QUEUE LIMIT:  The Queue Limit defined in the Admin Server tab is renamed to Import Limit. Previously the queue limit was considering documents after separation. Assume that your queue limit was set to 100 and you would import PDFs which were separated in 200 individual PDFs, then this would cause the MetaServer to pause importing until 101 of the separated 200 PDFs would be exported before importing another document.

The new Import Limit which replaces the Queue Limit works differently and checks the number of imported files and disregards any separation action after import.

In our example with an Import Limit of 100, importing a PDF which is separated in 200 PDFs will not pause importing anymore and will continue to import until 100 PDFs are imported.  Of course if each of these 100 PDFs would be separated in 200 PDFs, your MetaServer queue would grow to 100 x 200 = 20.000 documents which is too high. So adjust you Import Limit and avoid exceeding 10.000 documents (after separation) at one time in the MetaServer queue. Ideally you never have more than 1000 documents in the queue.

In the client’s status bar and the document counters window, you can see at any moment how many documents are imported and how many are in the queue.

This is an important change implemented for load balancing where multiple MetaServers are watching the same watched folders.  The new Import Limit will make sure that all servers will import an equal amount of documents regardless of any separation action.

Version 3.0(13) | 2019-06-19

– ENHANCEMENT: Direct SQL Server Lookups and Export to Database: We now also list views in the tables list and you can search in views.

– ENHANCEMENT: Workflow ON / OFF button: If the workflow is switched ON, the power icon is now green instead of red. If it the workflows is switched OFF it is red instead gray.

– ENHANCEMENT: We added “Copy DB Connection Settings” to copy all DB connection settings (not the lookup and mapping) from one rule to another regardless the type. So the settings can easily be copied between Find Word, Find Word Group, Validation DB Lookup and DB Export. We already did this with SMTP settings and it made sense to do the same with DB settings.

– ENHANCEMENT: SELECT SERVER: When the operator presses the menu part of the select servers button, show previously connected servers to do fast switching between MetaServers without having to wait for the discovery.

Version 3.0(12) | 2019-06-13

– ENHANCEMENT: ADMIN CLIENT: SERVER TAB: Added 4, 25, 50 and 75 as possible values for the server queue. This in context of watching the same folder with multiple MetaServers.

– FIX: VALIDATION: Required option in combination with Check if blank ON or Always check ON made the field non-required if the field was not pre-populated.

Organizer tab
Validate Action
Organize Action

Version 3.0(11) | 2019-06-08

– ENHANCEMENT: Import from Folder: “Move file to” option: If the file already exists (locked or not locked) in the “Move file to” folder, the moved file generates a new file with a sequence number (x). This avoid errors when the file is locked and will also show if a file with the same name is imported multiple times.

– ENHANCEMENT: DB LOOKUP: More efficient handling of multiple DB Lookups.

– During Find Word. If the search field is looking up in an empty Source field, no lookup is done at all.
– During Check Validity: Identical lookups are only performed once.
– When Validation is opened: Field evaluation is not repeated right after Check Validity

Version 3.0(10) | 2019-05-30

This version requires .Net Framework 4.6.2 or higher on both the server and the clients. In case your .Net Framework version is not up to date, you can download the latest .Net Framework from here:

– NEW: Find word with Type and Validate: NEW TYPE (Check Digit): Numéro d’identité Luxembourg. You can now extract “Numéro d’identité Luxembourg” using a Find Word with Type rule. We make use of the check digit in the “Numéro d’identité Luxembourg” to locate it.  You can also use the same check in a validation rule and only numbers that have a valid check digit and length will be accepted. The “Numéro d’identité Luxembourg” is printed on les “Feuilles d’Impôts” (Tax Declarations) and makes extraction of this number extremely reliable.

– NEW: Find word with Type and Validate: NEW TYPE (Check Digit): KBC Bank Mod97 Checksum. You can now extract KBC Customer IDs using a MOD97 check (check digits 00 = 97) using a Find Word with Type rule. We make use of the check digit to locate it.  You can also use the same check in a validation rule and only numbers that have a valid check digit and length will be accepted.

– NEW: RESERVE FILES DURING IMPORT FOLDERS: This makes it possible to watch the same folder with several MetaServers for load balancing. For example 2 or 3 servers could watch the same folder to convert scanned PDFs to searchable PDF.

Version 3.0(9) | 2019-05-17

– NEW: REPLACE “TAB” (Long Space) WITH THE REPLACE TEXT RULE: Sometimes redundant TABs need to be removed from extracted text.

For example if a total amount is printed like this:
1000 . 00

The OCR result may result in this output:

This makes it impossible to extract the complete amount 1000.00 because it’s spread over different word groups. You can now fix such anomaly by using a Replace Text rule replacing “{ Tab }.{ Tab }” with “.”. This will remove the TABS surrounding the decimal point and leave any other TAB in the text untouched.

– NEW: VALIDATION – NEW OPTION  TO DISABLE POP-UP BALLOON MESSAGES:  If you use the field labels to explain what the user should enter, then you can now disable the pop-up validation error messages (e.g. This field is required. It cannot be left blank.) by disabling the option “[ X ] Show pop-up error messages during validation” in the Validation action.

– FIX: ORGANIZER JUMPED TO FIRST PAGE AFTER SEPARATE: When separating documents, the selection always jumped back to the first page of the document set making it hard to look for the next separation point.

Version 3.0(8) | 2019-05-15

FIX: DOCUMENT SEPARATION: If the last page of a document set was a separator to be separated “after the page”, an error occurred.

Version 3.0(7) | 2019-05-07

– ENHANCEMENT: SEPARATE DOCUMENT: 2 METHODS ALLOWED: We now allow 2 different separation methods in a single separate document action. For example you can separate on a barcode on the first page and separate on a barcode on the last page.

– ENHANCEMENT: ADMIN CLIENT: Remember last selected workflow: We remember the last selected workflow you worked on when re-opening Admin. Before the first workflow was always selected in the Workflows tab when opening the Admin client.

– NEW: HELP FILE: Edit – Calculate Time Span

– FIX: IMPORT FROM EMAIL: When moving emails to an IMAP folder after processing, they were correctly moved to the defined IMAP folder but only marked for deletion in the inbox. However, they were not purged from the inbox resulting in processed emails both showing up in the processed folder and the inbox. Moved emails are now correctly purged from the inbox.

– FIX: ADMIN & OPERATOR CLIENTS: MetaServerValidation.CBMSVSettings and MetaServerAdmin.CBMSVSettings are used to save information relevant to the clients, such as last used workflow, test folders, position of windows etc. When these files were damaged, the corresponding client would not start anymore. This is now fixed and we keep a backup of these files which we restore when the *.CBMSVSettings is damaged. If the backup is also damaged, we load the client with the default settings.

Version 3.0(6) | 2019-05-01

– FIX: Import from Folder: Before, when files were placed in the MetaServer watched folder(s), they could not be deleted or renamed anymore. Also opening them in a PDF viewer would make MetaServer fail.  This version handles these conditions gracefully.

1) Deleted files are now ignored.
2) Renamed files are imported under the new name.
3) Locked files (for example when a PDF file is opened in a PDF viewer) are skipped until they are unlocked.

– ENHANCEMENT: Find Word, Validation DB Lookup, Export to Database and Stored Procedure: MS SQL uniqueidentifier field type is now supported in the mapped fields and stored procedure.

– ENHANCEMENT: SELECT SERVER: The Select Server list now also shows the API version. You can only connect with a MetaServer with the same API version as the client. If the API versions don’t match, the MetaServer will be listed but marked in gray.

Version 3.0(5) | 2019-03-22

– NEW: Multiple Conditions in Set Field Value rule: You can now set up to three conditions combined with “AND” to set the value of a field conditionally. For multiple “OR” conditions, just define several SET FIELD rules like before.

Example 1: set “EMAIL TO” equal to “” if:

TOTAL AMOUNT is greater than or equal to 10000.00

In that case the manager will only be notified for orders >= 10000 that come from customer NEWCUST.

Example 2: Document type detection using keywords.  If for example you find keywords that classify a document both as ACKNOWLEDGMENT and OFFER then you can force this combination to for example OFFER with these settings:

Set DOCUMENT TYPE equal to OFFER if:


Version 3.0(4) | 2019-03-18

– NEW: MULTI-SELECT PAGES IN THE ORGANIZER: You can now select multiple pages using the CTRL-CLICK or SHIFT-CLICK technique, or select all pages with the CTRL-A shortcut. Once multiple pages are selected you can apply a function to all selected pages (documents), such as separate, merge, delete and rotate.

– FIX: When doing a MetaServer install without any of the sample workflows or demo files, C:\META-DEMO  was not created. This caused problems when creating an Extract or Separate action pointing to C:\META-DEMO as the Test Folder.  When MetaServer is now installed, it will create C:\META-DEMO automatically if it does not exist.

Version 3.0(3) | 2019-03-13

– NEW: UTF-8 BOM and UTF-8 option in Export to Folder: The file index can now be encoded in UTF-8 BOM or in UTF-8 format. Default is UTF-8 BOM. For more info about the byte order mark (BOM), see here: 

– NEW: Help button added to Find Number Extract Rule: 

– NEW: OK ALL BUTTON IN VALIDATION: This makes it possible to validate all green fields (valid but forced check) with a single click. The OK All button is optional and is by default disabled in the Operator Client. To enable it, open the Admin client and enable the OK All option in the Server tab. 

– NEW: The last selected test document folder is now saved as part of the workflow: If you now create an installer and include the last selected test document folder, it is automatically selected as the test folder on the target system. If the target system had a previous version of the workflow with another test folder already selected then the test folder does not change. 

– ENHANCEMENT: In Validation, the Drop Down List now automatically opens as you type in a database lookup field. 

– FIX: better handling of changes to test document folders: When previously used test document folders for testing extraction or separation rules for a given workflow were deleted or renamed, the test results were deleted on unexpected moments.

Version 3.0(2) | 2019-03-04

FIX: Find Word with Mask / Words in combination with the Keep All Matches did not work correctly anymore in 3.0.1 and concatenated all words found on the same line of text. Also finding words containing a string did not return the whole word but only the set string.

Version 3.0(1) | 2019-02-18

– NEW: EXPORT TO SAP R/3: This connector requires its own activation code. SAP Transport files are placed in C:\CaptureBites\MetaServer\SAP Transport.

Help is directly accessible from the setup and is located here.

Export to SAP R/3 exceptions are handled as follows:

1) BARCODE EXCEPTIONS: No open internal barcode (late archiving) or already existing external barcode (early archiving). A Document causing such barcode error is moved to the errors tab. However this does not stop the Export to SAP R/3 export action and documents with correct bar codes will continue to be processed. To solve the issue, adjust the barcode value in SAP and retry the documents in the Errors tab. Or delete the documents from the Errors tab and scan them with a correct barcode.

2) THE EXPORT TO SAP R/3 IS NOT LICENSED. Documents exported to non-licensed connector, are moved to the errors tab and the Export to SAP R/3 is halted (red state), documents in the MetaServer queue stay on hold until the problem is resolved. Apply for a license ( Activate the connector and publish and apply the changes to the current documents in the queue. Documents in the system will be correctly exported.

3) THE EXPORT TO SAP R/3 IS NOT CONFIGURED CORRECTLY. A wrong configuration typically causes an “unable to connect to SAP” error. The document is moved to the errors tab and the Export to SAP R/3 is halted (red state), documents in the MetaServer queue stay on hold until the problem is resolved. Resolve the configuration issue and publish and apply the changes to the current documents in the queue. Documents in the queue and in the Errors Tab will be correctly exported.

4) THE SAP R/3 TRANSPORT IS NOT CONFIGURED CORRECTLY. This will cause an “unable to connect to SAP” error. The document is moved to the errors tab and the Export to SAP R/3 is halted (red state), documents in the system stay on hold until the problem is resolved. You can find more documentation here.

Select the error document and retry the action to rety the export to SAP R/3 action. Documents in the MetaServer queue and Errors Tab will be correctly exported.

– NEW: IN WORKFLOWS TAB: DISABLE EMAIL ALERTS – We added an option to disable email alerts. In environments with unknown smtp settings, email alerts can now be disabled until correct SMTP settings are provided. The default for new workflows = Email Alerts OFF (no alerts). When the email alerts are switched off, the Alert icon in the workflows tab is gray. When email alerts are switched on, the icon is red.

Version 3.0(0) | 2019-01-11

– NEW: SEPARATE ADMINISTRATION CLIENT – All Admin functions have been removed from the Validation client (now called Operator Client) and moved to an all new MetaServer Administration Client.

MetaServer Administration Client

MetaServer Operator Client

– NEW: The Validation client is renamed to MetaServer Operator Client. You will now find two icons on the desktop:

MetaServer Admin:

MetaServer Operator:

– NEW: All functionality of the Admin and Operator clients are organized in a ribbon UI consisting of 6 tabs in Admin between 1 to 3 tabs (depending on hidden or exposed functionality) in the Operator Client.

Version 2.0(24) | 2018-12-12

– NEW ACTION: Convert -> To Black and White

The setup of the “Convert to Black and White” action is similar to the Extract Text setup viewer but only showing the black & white conversion settings.

The pages selection and conditional settings make it possible to conditionally convert specific pages or documents to BW based on index values. For example If the field “document type” is equal to vendor “FUZZY PRINTING INC”, then those documents will be converted to black & white.

As usual, the result would be exposed as Processed PDF or Processed TIF in the exporters.

Version 2.0(23) | 2018-12-12

– ENHANCEMENT: When you test extraction rules, the OCR result is saved as a *.ExtractTxt file. These files are now using a new .XtrTxt file extension. If you sort them by extension the are placed on the bottom of file list so you cannot accidentally copy them in place of the PDF files when testing your workflows.

– FIX: Extract: Extract Text Rule: The image was not displayed in black and white anymore when doing TEST. The test result is also not reused anymore.

– FIX: Convert to Format: Convert to TIF: Failed on Black and White PDFs or ePDFs containing images in black & white (eg signatures in electronic Floating data documents).

Version 2.0(22) | 2018-12-10

– ENHANCEMENT: Improved .Net Heap Memory management. Important for systems handling many documents per day.

– ENHANCEMENT: Moved Apply Separation action to a seperate *.exe to improve memory management.

– FIX: Opening the document list is now much faster.

– ENHANCEMENT: Updated Email and FTP libraries to Rebex 2018 R3 Build 6874.

Version 2.0(21) | 2018-11-20

– ENHANCEMENT: Reset the windows garbage collector every 100 lookups.

– ENHANCEMENT: Possibility to decrease the MetaServer queue to a lower value than 250

– FIX: Document set locking to avoid concurrent use.

– NEW: MFP Panel updated with Questionnaires instead of POD workflow

This version was never made public and only tested in beta at some customers (CLL & EAD).

Version 2.0(20) | 2018-11-14

– ENHANCEMENT: Improved prority handling of separated documents. Previous versions could cause a slow down or complete shut down if large volumes of documents were separated.

– ENHANCEMENT: Better error handling: Find / Lookup / Stored Procedure: list procedures: report error if a parameter data type is unexpected

Version 2.0(19) | 2018-11-14

– ENHANCEMENT: Improvement in the way delayed validate is handled. Delayed validate is used to allow a validation operator to go back one document to make correction.

Before documents were processed chronologically and got delayed even if the delay was already expred because following a document being delayed. Now documents are processed according to their delay expiration time and documents cannot get held up anymore because there is a document before being delayed.

– FIX: Apply Organize: Assign a copy of the field values to the new documents (fix for “Collection was modified; enumeration operation may not execute.”). MS_Workflow.Document.WfDocument.SerializeFieldValues(TextSerializer writer, IDictionary`2 fieldValues)

Version 2.0(18) | 2018-11-09

– ENHANCEMENT: The Convert to Searchable PDF is now running multi-threaded and runs 4 converter threads. Expect a speed enhancement between a factor 2 to 4 depending on the peformance of your processor.

– ENHANCEMENT: Better overall memory management

Version 2.0(17) | 2018-11-08

– FIX: SQL Direct: DB Lookup: Fixed a problem handling integers.

– NEW: Conversion of email body to PDF is now possible. However, this works with limitations. You can import emails, convert the body to PDF and export those PDFs to folder. You cannot do anything in between.

In the Export to Folder action, select Email PDF as the File Source to export the email body as PDF.

You cannot extract or validate after a “Convert Email Body to PDF” action. You would need to export the converted PDFs to another workflow’s watched folder to do extraction and validation etc.

Version 2.0(16) | 2018-11-07

NEW: We added a direct connection to SQL Server for all functions using a DB connection in MetaServer:

– Find Word using words from database
– Validation Database Lookup
– Export to Database.

When you use a direct SQL Server connection, you don’t require the setup of an ODBC data source anymore on the server or on any of the validation clients.

Because the communication with the SQL server is direct, searching and updating SQL tables is also more efficient.

Currently, only MS SQL Server is supported.

Version 2.0(15) | 2018-11-05

– FIX: Validation: DB Lookup: If a lookup was used with the option “check if multiple hits” and the lookup was filtered, then, even if filter returned a single hit, the field still stopped in Validation because of multiple hits.

– FIX: Extraction: Stored Procedure: If no Stored procedure was selected, the Connect button did not open the Stored procedure tab. This typically happened when you had defined a stored procedure rule from scratch.

Version 2.0(14) | 2018-11-01

– NEW: Lookup with Stored Procedure. You can now call MS SQL or My SQL stored procedures and use the returned results in MetaServer. This action can be found under the Find rules.

For example, if you have a list of expected documents for each case in a SQL table, then you can create a Stored Procedure that checks presence of a scan date for each document. If a scan date is present for all documents, the procedure can then return a value TRUE for completeness, if any of the expected documents don’t have a scan date, the procedure returns a value FALSE for completeness.

Based on the returned value, you can then trigger a notification email if all documents have been scanned.

Version 2.0(13) | 2018-10-22

– NEW: Integration of a new version of the OCR engine used for Text extraction. This version can recognize an extended character set including characters used by East European countries and Russia (Cyrillic).The new OCR engine also uses the selected language to improve OCR accuracy.Because the previous version of the OCR engine did not have a language setting, we use the Windows language to set the language when converting existing workflows to the new version. We recommend the settings of your “Extract Text” rules to be sure the adjusted settings match your configuration.

Version 2.0(12) | 2018-10-08

– NEW: Convert / Convert to Format action. With this action you can convert PDF files to Multipage TIF. The Multipage TIF output is exposed in the Exporters as “Processed TIF”. This to be roadmap compatible when we introduce importing TIF files. The original imported TIF will then be accessible as Imported TIF in the Exporters.The TIF format is available in the Export to Folder and Export to Email actions.We will add TIF support to future connectors as they get releases.

– NEW: Edit / Scale Page(s): With this new action, you can first extract data from a 300 DPI or 400 DPI scanned document, create a searchable PDF and at the very end scale it to a lower resolution for storage. In other words the high resolution version will be used to get the best OCR result and when all data extraction is done including creating the PDF searchable text layer, the image size is reduced. This only affects color scans and does not touch black and white scans or electronic PDFs. The Scale Page(s) action also allows to set the JPG Quality factor. Default JPG Quality = 82

– ENHANCEMENT: Export to Database: This version includes up to 5 DB connection retries if the connection fails, with a 0.5 sec delay between them.

– FIX: Export to Email: When the user did not put a file extension in the email attachment name, the MetaServer showed an error because of the missing MIME type. Since this version, the mime type comes from the selected file type if there is no extension specified.

Version 2.0(11) | 2018-09-28

Convert to Searchable PDF: We adjusted the logic to determine if a PDF should be converted to searchable PDF.

The logic is now: If the PDF only contains a single image and no text, a searchable PDF will be generated.

That means that:

– Text based electronic PDFs are not converted and remain untouched
– PDFs that are already searchable are not converted and remain untouched
– MRC (Super Color Compressed) PDFs contain multiple layers of images instead of a single image and are not converted and remain untouched.

For Extract Text to determine if a PDF is image only, nothing has changed except of considering a bit more margin (+1mm / -1mm) of the scanned image versus the PDF page size.

Convert to Searchable PDF: If nothing is entered in the page range, “Page(s): All” is displayed in the Actions list, otherwise the selected page range is displayed.

Version 2.0(10) | 2018-09-21

– NEW: Convert to Searchable PDF action: You can now convert image based (scanned) PDF files to searchable PDF files.

To get access to the feature, you need to install the MetaServer Searchabe PDF module which can be downloaded from here:

You basically add a Convert to Searchable PDF action to your workflow before Export.  In the Export action, you then select “Processed PDF” as the PDF you want to export.

Version 2.0(8) | 2018-08-28

– NEW VARIABLES IN THE DOCUMENT SECTION: “Document Number” and “Document Count” in set. A set is a single PDF with multiple documents. After separation, manual with the organizer or automatic with a Document Separation action, these variables are updated with the total number of documents after separation and the document number of each document.

– FIX: Find Word with Mask / Words in combination with “Accept words from database” was not accent agnostic, requiring to put all variations of accented words such as: PROCÈS-VERBAL, PROCES-VERBAL, Procès-Verbal in the DB. The search is now accent agnostic and you only need to put one variation. However this is only valid for MetaServer databases.

Version 2.0(6) | 2018-08-27

– FIX: Document Separation: If you add a separation point manually after automatic separation a red error occurs.

– FIX: Field values were lost after going through the organizer.

Version 2.0(5) | 2018-08-21

– Enhancement: Mark Detection: Faster processing when multiple mark detection rules are defined on the same page. Example: A questionnaire with 80 questions with each 5 options (a total of 400 check boxes to evaluate) took about 200 seconds to process before and now takes 35 seconds.

Version 2.0(4) | 2018-07-23

– New: Mark Detection: Mark detection allows to detect check marks or detect pixels in a large box like in a signature zone.

To get familiar with this new extraction rule, please try out the new CB – QUESTIONNAIRES and CB – PARKING VIOLATIONS demo workflows. Online help will follow soon.

Version 2.0(3) | 2018-07-19

Fix: Validation text selection tool on electronic PDFs did not work correctly anymore in 2.0(2). Selecting a zone, selected all the text on the page.

Version 2.0(2) | 2018-07-18

– New: New option in the Separate Document / Process action: “Rotate page like text in field…”. Just select a field with extracted text by means of OCR or bar code recognition and the page will be rotated according to the orientation of the majority of the text contained in the field.

– New: In the About tab in the backstage you now have a Version History button which opens the online version history page

– Enhancement: Separate Document / Process Page: When a new action is added, delete and separate options are now set to none by default. 

Version 2.0(1) | 2018-07-16

– New: Separate Document action: The Separate Document action is renamed to Separate / Page Processing and now includes additional page level processing options:

– Delete Separator: Allows to delete all pages detected as separator. Only “real” separators are deleted. That means if the first page of a set is not detected as a separator according to the separator rules but only is a separator just because it is the first page of the set, it is not deleted. This situation happens when scanner operators don’t put as separator page on top of the set because the first page is a document by default. Documents inside the set will have separators and those will be deleted.

– Delete “if value of field…” or conditional deletion: allows to delete a page based on the content of a field.

– The “Separate every page” is now “Separate every n pages” where n is an integer. By default it is 1 but can be set to any other value like every 2 or 3 pages… 

Version 2.0(0) | 2018-07-10

– New: Export to Folder: If file exists, Append or Prepend new pages to the existing PDF. Exception flow if the file is locked (typically when the to be updated PDF is open in a PDF viewer).

Exceptions can be handled in two ways:

1) The file name contains a “file sequence number” variable. If the file is locked, a new version is created using the file sequence number containing the pages of the locked PDF + the new PDF. The File locked condition applies and an email export can be used to warn the user about the lock issue and the creation of a second version.

2) The file name does not contain a “file sequence number” variable. If the file is locked, nothing happens, the File locked condition applies and an email export can be used to warn the user about the lock issue, the file that could not be appended or prepended can be attached to that email.

– Enhancement: More logically grouped Setup variables menus in all windows where variables can be picked from a Setup menu.

Version 1.0(30) | 2018-06-18

– New: MetaServer System Variables: Current Date & Time. These are useful to calculate the time span between two actions to log in a statistics DB or CSV file. You can calculate the time from before until after extraction for example or from workflow start time to final export time.

– New: MetaServer: Calculate Time Span: New Rule to calculate the time between two times. With this rule you can caculate the number of days between dates. If you also include a time element, you can calculate the time span with a precision to the second.

– New: Delayed Validate and Delayed Organize: You can now set a delay (default 10 seconds). During this time the last validated document remains available for further corrections. This is handy when the validation operator hits the ENTER key too fast by accident and realizes some more adjustments need to be made to the last validated document. With the Last Validated button the operator can go back to the last validated document and make further changes to the document and its metadata. 

Version 1.0(29) | 2018-06-11

– New: Export to Folder: If the export folder is set by a field and the field is empty, the document is not exported. You can then conditionally export a document by leaving the export folder empty, similar to exp. to email with empty email.

– Performance: The rules processing speed is considerably improved during both testing and run time

– Enhancement: ExtractTxt files, generated during testing of extraction rules and introduced in version 1.0.25 to speed up testing, are now automatically deleted when placed in a MetaServer watched folder. 

Version 1.0(28) | 2018-06-07

– New: If an action locks up because of mistakes in the workflow settings. You can know restart that action without having to restart the complete server. Just fix the mistake and then click on the red action in the Server tab, and press the Restart queue button. The action restarts instantly. Only red import action errors cannot be restarted individually, you still need to restart the server to restart import from folder and import from email actions.

– Fix: Field cells and type cells were editable instead of display only in DB Lookup mapping panels and in DB Export mapping panel.

– Fix: When importing email attachments, { Import Source File Full Name } and other import variables were empty during Extraction. They were correct when used during export.

Version 1.0(27) | 2018-06-04

– New: Export to Database: Export metadata to an ODBC compliant database. If you also want to update a field holding the path to the exported PDF file, use a Export to Folder action first followed by an Export to Database. Map the export path with any of your fields in the DB. You can have multiple Export to Folder actions in your workflow which each will update the export paths and each can be followed by their own Export to Database action. The Export to Database also supports the time element in DateTime fields. In that way it is possible to update a database table registering time of import and time of export of each processed document. The export to database is thoroughly tested with a variety of field types using MS-Access, MsSQL Server, MySQL Server and Excel.

– New: Extract: Replace Text: Fields are added to the setup menus of replace fields. 

Version 1.0(26) | 2018-05-21

– Fix: Extract: Electronic PDFs or Searchable PDFs disappeared in the text extraction rule viewer when extracting text in version 1.0(25). If you defined extraction rules with version 1.0(25), you may need to redefine them.

– Fix: Export to Email: MetaServer locked up when and invalid “email to” address was used or incorrect SMTP settings were configured. In this version, the erroneous export email action will turn red, the document that cannot be sent leaves the workflow and an error is emailed to the specified email address in the report error setup.

Version 1.0(25) | 2018-05-17

– New: Set Field Value: It is now possible to add the page number next to each line of a text extraction result. This is useful info if you need to know the page number where each line is located. For example to find all pages potentially containing a signature.

– New: Extraction: Test function: Save text extraction result. If text extraction settings don’t change, the text extraction rules are not rerun, speeding up testing.

– If you delete an *.ExtractTxt, it will be recreated when a test is run on that PDF. 

Version 1.0(24) | 2018-05-11

– New: Request Trial Function: If MetaServer is not licensed and user goes to backstage, we now show a message: “MetaServer not licensed. [I have an activation code] – [Request a Trial] – [Cancel]. “Request a trial” brings the user to a form with the computer ID pre-filled.

DB Lookup fixes and enhancements
– Fix: When a lookup field was not the first field to check, and the lookup field was required or always check, validation did not stop on the lookup field.

– Fix: If you edited an existing DB Lookup rule and you changed the lookup field, then the mapping list was not updated. The selected field was still in the list and the previously selected field was not exposed. 

Version 1.0(23) | 2018-05-07

– New: Set Field: New option: Replace line separators with [ ]. This allows to replace line seperator with a character of choice. The option is disabled by default and when enabled, the default replacement character is SPACE.

– New: Workflow Setup: Last used test images folder is now saved per workflow.

– New: Open Document: New option with check box: “Hide reserved”. This hides all items reserved by others. This setting is remembered per validation client. By default, it is enabled. 

Version 1.0(22) | 2018-04-27

– New: Set Field: New option: Replace line separators with [ ]. This allows to replace line seperator with a character of choice. The option is disabled by default and when enabled, the default replacement character is SPACE.

– New: Workflow Setup: Last used test images folder is now saved per workflow.

– New: Open Document: New option with check box: “Hide reserved”. This hides all items reserved by others. This setting is remembered per validation client. By default, it is enabled. 

Version 1.0(21) | 2018-04-24

– There is a new version of the API between MetaServer and the client. You can see this API version in the About tab of the backstage.

– A previous version of the client is not allowed with this version of MetaServer and vice versa.

– For File names, CSVs etc, tabs are always replaced using this logic: TABs around values without pink rectangles are suppressed, other TABs are replaced with SPACE even if all objects in the file name have positional data. 

Version 1.0(20) | 2018-04-16

– New Find Word: From MetaServer & ODBC Database: It is now possible to map fields with the lookup results if Keep first or Keep last match is selected. Thanks to this, you can instantly see the lookup result during Validation and if necessary use the looked up value to set other conditions.

– New: Find Word: From MetaServer Database: It is now possible to load a MetaServer data source from a field to dynamically switch Database in the same workflow.

– New: Validation: Database Lookup: It is now possible to load a MetaServer data source from a field to dynamically switch Database in the same workflow. 

Version 1.0(19) | 2018-04-11

– New: Export to Folder: Index files can also be updated on an FTP server.

– New: Export to Folder: New Overwrite option to overwrite existing PDF files or File index files instead of creating copies.

– New: Separation and Extraction: You can now read Patch Codes with the Extract Barcodes rule.

– New: Separation and Extraction: Set Field Value: It is now possible to select a range of segments based on one or more separators for example select from 2–1 (the 2nd segment until the last) based on SPACE as the separator. 

Version 1.0(18) | 2018-04-06

– New: Update File Index in Export to Folder when it has the same name. This makes it possible to put all index data of a group of documents. For example all index data originating from the same scan batch or scanned the same day.

– Fix: When a document ended with a separator, the separator was deleted.

Version 1.0(17) | 2018-03-23

– New: Document Separation: Unattended document separation: You can now peform document sepration without an Organize action for fully unattended document separation.

– New action: Edit / Delete pages: With this action you can delete pages from PDF files. Typically, the action is used to delete the first page and get rid of the separator page. If all pages are deleted, there is a separate flow to process PDF without pages. The PDF without pages still contains the pages before the delete action. Deleting any of the pages does not affect the document index.

– New: Document Separation: If you separate every page, it is now also possible to extract data from each of the pages in the separation action. Previously it was required to run a separate extraction action to do this. 

Version 1.0(16) | 2018-03-19

– Added TEMPLATE WORKFLOW that can serve as a basis when creating a new workflow

– Export to Folder: Export file index to FTP is now implemented.

– Fix: Calculate Number / Date: Location of the extracted date (pink rectangle) is lost after a calculation.We now take over the coordinates of the source field and if it doesn’t have any, we take over those from the field used in the calculation formula.

Version 1.0(15) | 2018-03-16

– New: Document Separation Action – Document Separation can currently only be used if followed by Organizer action to view the result of the Document Separatio.

– Improved Bar Code Setup – Zonal Barcode – Conditional barcode reading – Reading barcodes only on specific pages.

– New bar code defaults: Default Skew Tolerance is now 5, Selected types are: 39, QR and 128

– New: Extraction – Edit – Calculate Number rule to add, subtract, divide and multiply values. 

Version 1.0(14) | 2018-02-16

– Fix: Time out error when publishing workflows

– New Extraction Rule: Find / Find Line with Number

– New: You can now search in the text result when testing extraction.

– Validation Select Text Tool: You can now select more than one line with the Select text tool and the lines are correctly concatenated in the field.

– New better defaults when creating a new workflow. 

Version 1.0(13) | 2017-01-15

– Email Import can be used to import PDF attachments via IMAP.

– After import the PDF attachments are processed in the same way PDF files imported from folders.

– Once all attachments are processed, the corresponding email message is archived. The archive action can be configured to keep the processed email in the inbox, move it to another IMAP folder or delete it.

– Emails without PDF files or only containing non-PDF attachments are always rejected. Rejected emails can be processed with other actions. 

Version 1.0(12) | 2017-08-18

– Floating Data Workflow
– DPE (Diagnostic Performance Energetique) workflow with Doc. Sep and DB Lookup