Category: iPaper

iPaper Client – Version 3.0.84 – New actions implemented

Innovations– iPaper 3.0.84:

  • Stationery as an additional action

The iPaper Client can under- or overlay a PDF letterhead. This function is located on the “Stationery” tab and represents an essential basic function of iPaper. Now, as with iPaper Server, there is also the option of adding additional “Stationery” actions, either once or several times, to the action list. In this way, not just a single, but also several “letterheads, watermarks or stamps” can be applied to a document during processing.

 

  • The order of the stationery can be specified in the selection list

This makes it possible to change the order in which the stationery appears in the selection list and to define it freely. In a list, the stationery can be sorted in ascending / descending order according to name / creation or modification date, and can be moved up or down. This allows you to summarize the most used stationery at the beginning of the list for faster selection.

   

  • PDF / A or ZUGFeRD as an independent action

Until now, PDF/A /ZUFGeRD was a general function of the application and not implemented as an independent action. This means that the PDF/A or ZUGFeRD output, like all other actions, can be managed via profiles, action profiles and thus now also the PDF/A function can be linked to a letterhead, or iPaper mdx can be used to select an action profile. Since the PDF / A conversion can only be carried out once and only at a certain point in time, the PDF/A action can only be inserted once and the sequence cannot be freely defined, it is always inserted at the end of the list. The ZUGFeRD XML can also be deleted immediately after it has been successfully embedded in the PDF.

 

  • New action – definition of variables

A “variable” action has also been added. This allows variables to be specified and assigned a default value. The variables can then be used in other actions, e.g. can be called up and used as parameters in the “Email” or “Save as” action. A name is assigned or a default value is assigned during the definition. Variables can also be assigned values ??using an external variable file (* .var, *. Txt). This allows values ??from other applications to be passed as parameters to Paper Actions. An external variable file can also be deleted automatically after processing has been carried out.

To read variables from an external file, the name of the variable and a standard default value are added to the list of the action. This default value can then be defined and overwritten externally in the external * .var / * .txt file. A line with <variable name> = <value> e.g. “Test = 4711” inserted. This means that the “Test” variable (% Var.Test%) has the value “4711”.

 

   

  • New action – PDF compression and optimization

With the new standard “Compress” action, iPaper now also has the option of compressing and optimizing PDFs in order to create PDF files that are as compact as possible. In particular, PDF files, scans or images can be greatly reduced in size. In addition to the possible reduction in the resolution of the images, the best possible PDF compression (JPEG2000 / JBIG2) is also used. The result is smaller, more compact and optimized PDF files.

 

 

  • Functions of the action profiles

Action profiles can be – newly created, copied, renamed, deleted or exported as an XML file or imported again. The XML files of the exported action profiles can also be used directly as a template for the external iPaper XML control (via an external file or via the printout). This means that manual coding of the XML using an editor is no longer necessary. All configurations can be made interactively via the iPaper user interface in the actions and then exported as XML. This is much easier and safer than manual coding using an editor using the iPaper XML syntax.

 

  • API / .NET programming interface

The API is used to query and set certain iPaper functions from external applications or to start the processing of an existing PDF file by iPaper. In order to be able to use the iPaper API, it must first be activated in the iPaper Client under “General Settings”. To use the API from an external application, the “iPaper.Interface.dll” and the installed and started iPaper Client are required. To demonstrate the available functions, two .NET / C # demo & test applications are available in the source code and as executables as EXE.

iPaper 3.x Client Version

Download GhostScript 9.53.3 64bit Setup

 

iPaper MS-Office Plugin Version 1.0.6 available

Ab der aktuellen iPaper Client Version 3.0.82 kann der neue iPaper Microsoft Office Plugin installiert und verwendet werden. Damit können die wesentlichen iPaper Funktionen direkt aus MS-Word bzw. MS-Excel heraus gesteuert werden. Ein eigener “iPaper PDF” Button erzeugt direkt, ohne Druckvorgang, aus MS-Office heraus eine PDF Datei, welche sofort von iPaper is processed further. The selected letterhead is used and the subsequent processing steps are carried out on the basis of the selected action profile.

iPaper MS Office plugin functions:

  • Generates a PDF directly from MS-Word / MS-Excel, without printing, for further processing by the iPaper Client
  • Select stationery
  • Selection of the action profile for further processing
  • DropZone – switch on / off
  • Query options – switch on / off
  • Queue – switch on / off
  • Show queue
  • Embed source document – yes / no

A new function, which is not available with the iPaper Client alone, offers the possibility of embedding the original document as DOCX / XLSX directly in the generated PDF as an attachment. This makes it possible to archive the PDF together with the editable original file in a single file or to pass it on to others for editing.

Requirements:

  • iPaper Client from version 3.0.82 – installed and started
  • iPaper Client API / “General Settings” activated
  • MS-Word / MS-Excel – MS-Office – 32 or 64bit – current versions

The iPaper MS Office Plugin uses the iPaper API interface to communicate with the iPaper Client application. Since the iPaper API is not active by default, it must first be activated. Then iPaper must be closed and restarted.

        

iPaper Client – Version 3.0.68 – Overlay / fill in PDF forms, link action profiles with the stationery

Innovations – iPaper 3.0.68:

  • Link stationery to an action profile: Action profiles offer the option of saving several actions with all settings in the desired processing sequence under a name and selecting them for further processing during runtime. Now it is also possible to link an action profile to a letterhead. If the stationery is selected manually or automatically using the mdx option, the associated action profile is automatically loaded and used for further processing. If <none> is selected for the link, the user can interactively select and load the action profile during runtime using the “Query options” function.

With this possibility, the further processing of the documents can be automated with the help of the iPaper mdx option. Documents can be recognized based on their content and further processing can be controlled and automated via it. The user no longer has to decide each time and select which further work steps have to be carried out for which document.

 

  • New action to overlay PDF forms:
    • With the new action “Form overlay”, a PDF form can be selected which is overlaid on the iPaper result PDF in order to generate a new PDF form.
    • The template form can also be replicated on the following pages. So that the field names in the newly created form are unique, the fields added per page are numbered.
    • The form fields can be filled with data from the document – with text or variables read from the document using the iPaper mdx option.
    • A separate variable is available for each field for the field contents that already exist in the form. Existing field contents can be transferred to the newly created form.

   

  • Updated iPaper PDF printer driver:  The iPaper PDF printer driver has been updated to eDocPrintPro Version 5.0.0. This version now supports and installs the current GhostScript GPL version 9.53.3.
  • Updated iPaper mdx option: The mdx functions integrated in iPaper have been brought up to date with PDFmdx.

iPaper 3.x Client Version

Download GhostScript 9.53.3 64bit Setup

iPaper Client – Version 3.0.66 – Alternative A3 letterhead with automatic selection

Alternatives A3 Briefpapier:

So far you could e.g. an A4 portrait format letterhead only define an alternative A4 landscape format letterhead, which was automatically selected and used during processing.

Especially when company balance sheets are drawn up by public accountants and tax advisors, balance sheets and profit and loss accounts are often output in tabular form on A3 landscape format. With the current iPaper Client Version 3.0.66 it is now also possible to use a second alternative, e.g. Configure A3 letterhead, which is then automatically used for landscape formats larger than A4. This means that overall balance sheet documents including the general terms and conditions appendix and cover sheet can be created in one step, with A4 / A3 portrait and landscape format stationery.

   

iPaper 3.x Client Version

Download GhostScript 9.50 64bit Setup

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.