iPaper 3.x – MDX Option – Product Video available – Read content and use as variables

For iPaper version 3.x there is the “MDX – MetaDataXtraction” add-on module. Key features of the PDFmdx application have been integrated into iPaper. Documents can be recognized on the basis of content, the corresponding stationery can be selected, or field, template and layout definitions can be used to read out information from the document. Fields / variables are filled with values which can be used later on in the iPaper actions. Fixed information or information read from the document can also be “stamped” on the PDF as text or as 1D / 2D / QR barcode.

iPaper MDX applications:

  • Automatically select the stationery to be used on the basis of the document contents.
  • For serial letters or document stacks it can be recognized at which page a new document begins to select the stationery again or to start again with the first stationery page.
  • Read e-mail addresses from the document and use them to send the document immediately.
  • Documents can be recognized on the basis of criteria, fields can be read out of the document via layout masks, variables can be assigned and used for iPaper actions such as e.g. e-mail, save as, program call and so on.
  • QR code barcodes (e.g. For quick transfers), 1D / 2D barcodes or text stamps can be applied to vouchers. It is also possible to assign read field contents from the document.

iPaper MDX Product Video – Read content and use as file name:

iPaper Client 3.x – .NET Interface – Control iPaper functions from own applications

With version 3.x of iPaper, there is now also the possibility via a .NET interface to query and set different functions and settings of the iPaper client from own applications. In order to illustrate the available functions or to be able to test, a C # sample project including source code and executable application is available.

Externally controllable functions:

  • Start / stop iPaper processing
  • Display of available stationery
  • Selection of (standard) stationery
  • DropZone – show / hide
  • Request options during processing – yes / no
  • Activate Queue – Yes / No
  • Show Queue
  • Display configured actions as a list, activate / deactivate actions from the list.
  • Export / Import Settings

Download – iPaper Client 3.x – .NET Interface – C# Sampleproject >>>

iPaper Client – Version 3.0.40 available

Innovations – iPaper 3.0.40:

  • Use last stationery as standard –  If this option is checked, the recently used stationery will be set as the new default stationery. If this option is not ticked (default setting) – in the “Query options” processing – the “standard” stationery selected via the configuration or via the Icon Tray function is always selected, irrespective of which stationery was used during the last processing.

  • AutoPrint “Action – default printerIf the option “default printer” is ticked, then in the “query options” processing the default printer set in the operating system is displayed for information.

iPaper 3.x Client Version

GhostScript 9.21 Setup

iPaper 3.x – Actions – Product video available

iPaper can further process the generated document with a PDF letterhead using “Actions”. There are various actions available.

Available iPaper actions:

  • Insert attachments,
  • AutoPrint – printout on a physical printer,
  • Insert backsides,
  • EMail,
  • Insert / add PDF at beginning / end,
  • Fill in PDF info fields,
  • Call external application via command line with parameter,
  • Save as,
  • PDF encryption / document protection,
  • PDF signature / timestamp,

Actions can also be inserted and configured several times in succession in the action list. All active actions are performed in the order specified.

This iPaper 3.x product video shows how actions can be inserted, configured and used in the action list:

iPaper 3.x Client Version

GhostScript 9.21 Setup

iPaper 3.x – Introduction – product video available

With the availability of iPaper version 3.x, there is a new introductory product video showing the key features of iPaper:

  • Stationery underlay,
  • Use single or multi-page stationery,
  • PDF printing from an application or PDF processing via DropZone.

iPaper 3.x Client Version

GhostScript 9.21 Setup

iPaper – Automated installation

An automated iPaper installation consists of the following parts:

  1. The installation of the version of GhostScript suitable for the iPaper version.
  2. Installing the iPaper application.
  3. Retrieve the license and activate the software.
  4. Configuration / distribution of the presets.

Normally our setups are executed as EXE. The EXE setup contains both the 32bit and the 64bit MSI of the application. With the EXE installation certain automated steps are executed automatically. The installation prerequisites (eg .NET Runtime, presence of the correct GhostScript version, etc.) are checked and if components are not available or not in the correct version, they are downloaded from the Internet and pre-installed. Likewise, the EXE setup decides whether on the computer the 32 or 64bit version must be installed.

Automated installation requires MSI installation packages. If the MSI packages are used, the installation prerequisites must be established correctly. It is also necessary to specify which version (32 or 64bit) has to be installed.

The “iPaperNET Client.exe” setup contains the required MSI files – but these must be extracted from the EXE.

Extract MSI from EXE:

  • /extract <path>Extracts the MSI contained in the EXE into the specified path. If the path contains spaces, it must be surrounded by quotation marks.
  • Beispiel: “C:\iPaperNET Client.exe” /extract “C:\temp” – This command-line command extracts the MSI to the folder “C: \ temp”

A description of the parameters can be found here >>>

Depending on the operating system, the 32 or 64bit GhostScript version must be installed – for iPapers up to version 2.99.1 the GhostScript version 9.18.1 is required.

Example Extracting the MSI and installing 64bit versions:

  • “C:\temp\iPaperNET Client.exe” /extract c:\temp
  • msiexec.exe /i “C:\temp\gs918.1×64.msi” /quiet
  • msiexec.exe /i “C:\temp\iPaperNET Client.x64.msi” /quiet

Retrieve the iPaper License:

To retrieve the licenses from our license server, this can either be done interactively via the installed PAM (Product Activation Manager) or via Commandline

  • “C:\Program Files (x86)\Common Files\MAYComputer\LicMan.exe/ACTIVATE MULTI=“AUTO” USERID=“user” USERPW=“passwort” APPID=“2PC” /SILENT

In the example, “user” and “password” must be replaced by the PAM login information. The AppID “2PC” is used up to iPaper version 2.99.1.

iPaper Configure and distribute presets:

All settings of the iPaper application are stored in the iPaper.xml file in the default path (C:\Users\%user%\AppData\Roaming\iPaper.NET\iPaper.xml)

If it is not found there then:

  1. Checked if an iPaper.xml exists in the iPaper installation folder
  • If it is found there, we automatically copy it to the default path
  • If it can not be found in the installation folder, then 2.) is executed.

2. It is checked whether the xml file exists in the ProgramData directory C: \ ProgramData \ iPaper.NET \ iPaper.xml

  • If it is found there, we automatically copy it to the default path
  • If the file is not found there, an iPaper.xml file with predefined (fixed-coded) default settings is generated and stored in the standard path.

To specify default settings, we recommend variant 2.)

In the iPaper.XML you can use absolute path data or system variables.

Download – Example iPaper.XML

In this example, the system variables% HOMEPATH% and% APPDATA% were used. This makes general presets and actions which can be used universally for all users.

! Note that the iPaper.XML is always written / overwritten when you exit iPaper. So you have to replace the application before you want to replace it. Otherwise the file will be overwritten with the last values from the user interface when you exit iPaper.

Autostart – Run the application automatically when it starts – iPaper / eDocPrintPro

Some of our applications, e.g. iPaper.exe or other eDocPrintProMonitor.exe must be started automatically when the computer is started. If this is not done, however, you can check it yourself and correct it.

Normally, applications that are automatically started should be registered here:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

If a 32bit application is to be started automatically under a 64bit drive system, this is registered here:

  • HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run

Example iPaper:

Autostart von 32bit Anwendungen auf 64bit OS

Example eDocPrintPro incl. Additionally attached printer “Test”:

Autostart von 64bit Anwenduingen auf 64bit OS

iPaper – 100% Terminal server utilization by virus scanner

Almost every company uses virus scanners on both clients and servers. Most recently, one of our customers had a problem that after an update to the latest version iPaper, server utilization has risen by a few registered users to 100%. DThe problem is caused by the virus scannert.

To solve the problem, the following files had to be explicitly excluded from the virus monitoring:

  • iPaper.UI.exe – iPaper Program Folder- C:\Program Files (x86)\iPaper.NET
  • iPaperPDF.exe or with newer versions also monitor iPaperPDFMonitor.exe at C:\Program Files\Common Files\MAYComputer\iPaperPDF

iPaper – Start takes a long time – no internet connection

For security reasons all our Setup’s and applications are using a SHA-256 “Code Sign Certificate” signed by Symantec However, there are installations in which the e.g. (Citrix) terminal server also for safety reasons has no connection to the Internet. If now called a signed application, the validity of the signature is checked and this may require an Internet connection. Where there is no Internet connection, so the startup can take a long time, because first a “timeout” expires before the application starts.

In order to enable in this case a quick startup, the verification of the signature can be disabled. Given the configuration file named ipaper.UI.exe.config must be copied into the iPaper program path C: \ Program Files (x86) \ iPaper.NET.

Download – ipaper.UI.exe.config >>>

Note:

  • When a document or a program is digitally signed, or the root certificates are not actual, so Windows tries to execute a signature validation on the Internet. If no Internet connection available, this process runs in a time-out and will be continued only after some time. This application seems inactive, or need very long to start.
  • This configuration file should not be used when an Internet connection is available
  • The file tells MS-Windows to make no signature verification on the Internet

iPaper Version 2.99.1 available

The version 2.99.1 is based on the latest version 3.23.5 eDocPrintPro and Ghostscript version 9.18.1. The Setup detects an existing iPaper installation and updates automatically. The Ghostscript version 9.18.1 required for this version is downloaded automatically during the installation from our FTP Server and be installed. If there is no active internet connection available so Ghostscript can also be manually downloaded and previously installed. The setup will detect this and therefore can be installed even without access Internet.

Download – iPaper 32 & 64bit >>>

GhostScript 9.18.1 Setup

Download – GhostScript 9.18.1 MSI Setup – 32bit (ca. 16MB) >>>
Download – GhostScript 9.18.1 MSI Setup – 64bit (ca.16MB) >>>