Month: October 2016

PDFmdx – Version 2.8.1 available

Innovations PDFmdx Version 2.8.1:

Template synchronization:

The PDFmdx template editor can now match the locally created templates and layouts via a web service connection to one or more PDFmdx servers. This allows templates to be developed and tested locally, to be replicated to the processing servers later. Communication is via SOAP via http / https. This considerably simplifies and accelerates the matching and distribution of new and updated templates.

8_PDFmdx Editor - Abgleich von Vorlagen und Layouts mit entfernten Servern_#1  9_PDFmdx Editor - Abgleich von Vorlagen und Layouts mit entfernten Servern_#2

Textstamp with rotation angle

To apply a text not only horizontally, but at any angle, there is now the additional “angle” parameter.

6_Text-Stempel mit Drehwinkel Option  7_Text-Stempel mit Drehwinkel Option - Ergebnis

Anchor Field Search – New Features:

So far, the string for the positioning of the anchor field on the entire page has been searched (from top) and the first reference was assumed as the position for the anchor field. However, it may occur that the term is not the first but the next occurrence is the search position, and there is no other unique way to position the field over a search string. Therefore the function was extended.

By default, the anchor field search is now performed from the field position of the template. The next matching string is taken as the position for the anchor fields. A new addition is the ‘hit’ option. If it is activated and a number is specified, the page is scanned from top to bottom and left to right for the anchor text. The number indicates the number of hits as an anchor field position. So eg. the 2nd hit can be found on a page as an anchor field position.

4_Anker-Felder mit Teilstring Suche - Such-Treffer Nummer kann angegeben werden


Especially in the case of scanned documents it can happen that the contents of the documents on the page vary not only in their positioning horizontally or vertically, but documents can also have different scaling and sizes. Z.B. For example a scanned expression with different scales was created. Although the relative position and size of the fields to be read is the same between the documents, the absolute values are different. The layout for the reading of the fields is created using a typical document and so far only considered the absolute distances and sizes of the fields. A document that appears about 10% smaller on the A4 page could not be processed, because the fields compared to the created layout both of the position so synonymous of the size does not fit. For this, we have now implemented an AutoScale function, which is able to automatically compensate for such different scaling to a certain extent.

5_AutoScale für Ankerfelder - gleicht Skalierungen der Dokumente aus

What is to be considered:

  • The layout should be created from the “largest” version
  • An anchor field must be used that can be found without partial string search. E.g. Via the string “Invoice” but not via “* Invoice *”
  • The “AutoScale” option must be activated.

Detect and remove blank pages:

When scanning documents, duplicate scans may contain blank pages (partially unprinted backs) in the document. Scanners do not always have a function to automatically remove them during the scanning process. For the further processing and archiving, empty pages are disturbing and should be able to be removed. With the current PDFmdx version 2.8.1 there is now a function to automatically detect and remove blank pages. The criterion for detecting a blank page is a threshold value which is set to 95% by default. We recommend a value between 95 and 98%. The value specifies the percentage of the “white pixels” on a page. A page is identified as “empty” as soon as the proportion of white pixels is greater than or equal to the set value, e.g. 95%. Blank pages are removed before all other PDFmdx processors are started.

1_Entferne alle leere Seiten aus den Dokument - vor dem Start der Verarbeitung mit Schwellwert-Parameter

Remove sides / blank pages after the separation pages:

If a document is split, the found separator page can also be deleted. New addition is now also a function to delete the following pages of the separation page. In this case, either a certain number of subsequent pages to be removed can be defined, or the function for automatic page identification / removal with threshold values can be used.

2_Entferne leere Seiten nach der Trennseite mit Schwellwert Parameter  3_Entferne eine eingestellte Zahl an Seiten nach der Trennseite

Regular Expression Parameters to selectively extract numbers from a field:

RegEx expression “\ d +” can be used to return numbers of a field. If no parameter is specified, we automatically return the “first of the longest of the found numbers”. (E.g., the read-out field content is “page 15/110”, “110” is returned). Together with the “Hits” parameter, a number of a specific position can be extracted from the string. With parameter = 1, the first number found in the string “15” is returned with 2 the second “110” and so on.

RegEx can also be used in combination with the additional string formulations:

Up to now, only the RegEx processing or alternatively the other string processing functions could be used. Now it is also possible to combine these two functions – RegEx can therefore be used together with the functions – partial string, remove – left / right / space / leading zeros as well as the function characters and type selection. The RegEx processing is executed first, regardless of the type of the field.

%TIME% VariableNow in 24 hour format

Update to SQL Compact Version 4.x – The version is now already included in the setup and does not have to be reloaded and installed as usual with version 3.5.

Download – PDFmdx Template Editor & Processor >>>

FileConverterPro (FCpro) – Version 1.0.50 available

Innovations FCpro Version 1.0.50:

FCpro – Profilmanager:

With FCPro, the conversion parameters are managed via profiles. If several FCpro servers are operated, it is useful and necessary to keep the processing profiles of all FCpro systems synchronized. Up to now, this was only possible via a manual export / transfer and import of the profile files. With the version 1.50.0 there is now a separate FCpro profile manager which makes the adjustment between the servers much easier.

FCpro - Profil Manager - Remote Profil Verwaltung und Synchronisation  FCpro Profiverwaltung - Export und Import der Verarbeitungs und PDFExport Profile


  • Connection to the FC per server (description, URL, Username, Password, version info, main server – Yes / No, test the connection)
  • An FCPro server is set as master / main server, from which all profiles are replicated to the other servers.
  • Communication with the FCpro servers takes place via SOAP Web Services (http / https)
  • Retrieve FCpro server info and server statistics
  • Remote administration of processing and PDF export profiles (Export, Import – Selective or All)
  • Synchronization from the main server to all FCpro servers. (Processing and PDF export profiles)

Updating of all basic components up to date

Update of the .NET Runtime from version 3.5 to version 4.0:

  • Better performance than .NET 2.0 or 3.5
  • Reduced installation scope. Only 40 MB instead of 250 MB version 3.5 are downloaded and installed.
  • .NET 4.0 is already preinstalled / activated on the newer versions of Microsoft OS (Windows 8.1, Windows 10, Server 2012,) and therefore does not have to be activated manually via the control panel like version 3.5. However, the minimum requirement is Windows 7 SP1. Windows XP and Server 2003 are no longer supported by .NET 4.0.
  • The FCpro setup checks whether .NET 4.0 is installed on the computer during installation. If not, .NET 4.0 is downloaded and installed over the Internet.

Download – FileConverterPro (FCpro) ~190MB >>>