Print service plugin

Plugin-Download (requires login)

Xima® Formcycle Version 7 requires the Print-Service plugin version to be 4.0.0 or higher.

The plugin Print Services is available separately and lets you create a PDF document from a form that is optimized for printing. This plugin is subject to additional charge.

Technical details

To use the Print-Service plugin, it is necessary to install Node.js and the Print Server. This can be installed on the same server as the Xima® Formcycle master server.

Installation Print Server on Windows

The installation of the required Print Server requires different procedures depending on the operating system.

Installation of Node.js

1. Download the LTS version from
2. Run the MSI file
3. Run the wizard steps, leaving default settings as they are

Installation steps for the Print Server

4. Download the Print Server installation files from the Customer Cloud here.
5. unzip the ZIP file "" and move the content to the folder print_server_fc under C:\Programs\.

To install, open the command line (cmd) with administrative privileges and execute the following commands:

cd C:\Programs\print_server_fc
npm install
npm install -g node-windows
npm link node-windows
node install-windows-service.js

There now exists a new service FORMCYCLE Print Server. Please check if this is also started before you run a test. The script install-windows-service.js contains default variables for installing the print service.

  • The service is installed on port 8090 by default. To change this, you need to adjust the --port=8090 parameter in the install-windows-service.js file.
  • Logging is enabled by default. To change this set the parameter --verbose=true to --verbose=false.

After the installation, a folder named deamon is created for the log files.


Für die Deinstallation des Print Servers, öffnen Sie eine Kommandozeile (cmd) mit administrativen Berechtigungen und führen Sie folgende Befehle aus. 

cd C:\Programs\print_server_fc
node uninstall-windows-service.js

Installing Print Server under Linux

  Contrary to earlier versions, you need to copy ALL files from the ZIP file with the print server.

Installation steps for installing Node.js and the Print Server

To install, open the console and run the following commands:

# Loading the script (varies depending on the operating system)

#   Debian 10 - If you are logged in as root:
wget "" -O

#   Debian 10 - or if you are logged in as a normal user with sudo rights:
wget "" -O

#   Ubuntu 16 - If you are logged in as root:
wget "" -O

# Make file executable
chmod 750

# Start installation

# Run Print Server
systemctl start printserver

In the first lines of the script - via the variables PRINTSERVER_USER and PRINTSERVER_USER_PWD - the user name/password to be created can be adjusted.
The verbose parameter can be used to enable/disable the log output. The scripts for the service should be located at /home/formcycle/print_server. In the start script the verbose parameter can be adjusted.

Translated with (free version)


To uninstall the Print Server, open a command line (cmd) with administrative privileges and execute the following commands: 


During the installation, depending on the existing system, some Linux packages such as nodejs were also installed. However, it is not possible to uninstall the packages automatically. Delete the automatically installed packages only if you are 100% sure that they are no longer needed!

Using IPv6

Starting with version 2.0.1, the server binds to both IPv4 and IPv6 addresses by default, using the dual stack feature supported by most operating systems. Should that fail, the print server binds only to IPv4 addresses (

If required, you can also set a different bind address via the command line parameter "bindAddress".


To check if the installation was successful, the service can be called on the local server for a test (in that case it should be printed the website):


Plugin setup

Print-Service Plugin Installation

In order for the plugin to be available in Xima® Formcycle as an action in the workflow, it must be deployed in the System Plugin section of the management interface. Instructions for installing plugins can be found here.

If the old version of the print service plugin (phantom plugin) was already installed, the following procedure is recommended for installation:

  • Disable the phantom plugin
  • Delete the phantom plugin
  • Upload new print service plugin
  • Proceed with the configuration

Plugin configuration

After the plugin has been installed, the service URL must be adjusted. This is defined in the plugin via the mandatory parameter

If the installation was done on the same server as Xima® Formcycle, then specify localhost as the domain. If no changes have been made to the port, the setting 8090 is retained.

For example: http://localhost:8089/pdf

This completes the setup of the print service plugin and it is available as an action in the workflow processing.


Command npm not found

Under Windows it is possible that after the NodeJS installation the environment variables are not set correctly and so npm install cannot be executed. This was also the case if the default path under C:/Programs was not used during the NodeJS installation. So check in the path if these are existing. The following must be done for this:

  • Call up the environment variables via Control Panel > System > Advanced System Settings > Environment Variables button.
  • In Path you should find the following entries: C:\Users\{username}\AppData\Roaming\npm;C:\Program Files\nodejs
  • Confirm everything with Ok. The console then be opened again with admin rights.

Command npm install leads to timeout

If the npm install command does not work due to a proxy, then the general proxy setting is not sufficient. Therefore, the following must be executed via console:

npm config set proxy http://proxy.domain:port
npm config set https-proxy https://proxy.domain:port

If user data is required:

npm config set proxy http://user:pass@proxy.domain:port
npm config set https-proxy https://user:pass@proxy.domain:port

More information can also be found here:

Printing does not work

If printing via Xima® Formcycle is not possible, the cause could be that the print service is not reachable. This can be solved by the loopback URL. Under System > General > Loopback URL, loopback base URL: http://localhost:<port>/formcycle

PDF is printed, but the message 404 appears

In this case the print service works correctly because a PDF is already created. It must be checked whether the loopback URL is entered correctly so that the URL to the print service is resolved correctly.

Downloading Chromium fails

The following error message appears on the console after running "npm install":
Error: unable to verify the first certificate

The described steps are only a workaround and the environment variables should be set back to the default values after the successful installation!

PS C:\test> npm set strict-ssl false

Usage and options

To use this plugin, go to the workflow processing configuration, click on new action and select this plugin. The following options are used to configure the plugin action:

File name
File name of the created PDF document.
Print mode
Input elements as text: Input elements are converted into plain text fields and the form is adapted to the width of the page.
Print mode
By default, are form fields such as input fields and select fields are converted to plain text. If you choose to disable this conversion, no changes are made to the form and it is printed so that it looks as closely as it does in a web browser as possible.
Zoom factor
Scale factor for the form. Use this to magnify or scale down very large or very small forms.
Blank form
(requires at least print plugin version 4.2.0 and print service version 1.4.0) Can be used to create PDF documents that can be printed out and filled out manually with a pen. When enabled, all form field values are cleared and all hidden fields are shown. In addition, the maximum number of element repetitions are created.
User groups
A virtual user is created when opening the form with Selenium. Select the user groups here to which this virtual user should belong to. Form elements can be configured to be displayed or editable only for certain user groups.
URL parameter
Additional URL parameters added to the URL used when opening the form with Selenium. You can use URL parameters to prefill form fields or access them from within JavaScript.

CSS adjustments

General CSS adjustments can be done via a corresponding media query:

@media print {
  /* general CSS for printing */

Please note this CSS is applied in other printing contexts as well, e.g. when the user prints the form via the browser directly.

There are a few special CSS classes available that are set only when the print service is used. These classes are always added to the form.xm-form element.(requires at least print plugin version 4.2.0 and print server plugin 1.4.0).

This CSS class is always set.
Added when print mode is set to Preserve form fields.
Added when print mode is set to Convert form fields to text.
Added when the option blank form is disabled.
Added when the option blank form is enabled.

Input elements

To optimize the form for printing, form elements of type input field, text area und select (Drop-Down) may be converted to plain text fields, if the print mode is set to Input elements as text.

Additionally, the CSS classes print and XSpan are added to the converted input element that can be used for styling them. For example, in order to change the font size, you can use the following CSS:

.print.XSpan {
 font-size: 18pt;
 font-family: serif;

To overwrite some properties of the default CSS shipped with Xima® Formcycle, use more specific selectors such as:

.xm-form .xm-content div.print.XSpan {
 font-size: 18pt;
 font-family: serif;

Most properties do not require this, however.

Enforce page break

To create a defined page break, the page-break attributes must be set via CSS. The corresponding container or element has to be selected via the xn attribute. Please note that the CSS property display must be set to block, otherwise no line break will be created. In this example, a line break should be created before the container div1.

[xn=div2] {
 display: block !important;
 page-break-before: always;

Avoid page break

The default setting for printing is that a page break is inserted after each page of the form:

@media print {
    .CXPage:not(:first-child ), .page-break {
       display: block !important;
       page-break-before: always;

In order to avoid breaks, the following rule needs to be defined in the CSS tab of the form:

@media print {
    .CXPage:not(:first-child ) {
       page-break-before: avoid;

Usage of other fonts

Technical requirements

In order for fonts to be used and embedded in the created PDF documents, it is generally necessary for them to be installed on the server running the Print-Server.

Inclusion via CSS

To include a font installed on the server for printing, it must be explicitly defined with a @media print query and set for use by the appropriate form elements. In the simplest case, this can look like the following example:

@media print {
    @font-face {
       font-family: 'DejaVu Sans';
       src: local('DejaVu Sans');
    .xm-form.modern *, .modern .XPage * {
       font-family: "DejaVu Sans";

Here it is especially important that the identifier entered at local() corresponds to the name of the font.

Legal notice

Fonts sometimes have very tightly defined license terms and are priced differently depending on their intended use. It should be noted that fonts for creating PDFs must be embedded in them, which for many commercial fonts requires a different license than for delivery via a web server for the purpose of displaying a web page in a web browser. 

In fonts of type TrueType and OpenType information about the embeddability of the font can be stored directly. Depending on what is configured there, a font may not be embeddable and will instead be rendered by the Print-Service-Plugin only as a vector graphic in the created PDF documents.

JavaScript adjustments

Sometimes you may have to execute custom JavaScript code before the form is printed. For this, you can use the function $.xutil.onPrint. Its signature is as follows:

function onPrint(callback: () => Promise<void> | void): void

This function lets you register one or more callbacks that are run before the form is printed. When a callback returns a promise, the print server waits until the promise fulfills before proceeding with the printing. In case the promise gets rejected, the error is logged, but the print is not aborted. Please note that you must register the callback before the form is printed, e.g. within a JQuery document-ready-handler ($(callback)).

For example, to run an AJAX request and wait for it to finish before the form is printed:

  $.xutil.onPrint(async () => {
   const response = await fetch("");
   // do something with response
  $.xutil.onPrint(function() {
   return new Promise(function(resolve, reject) {
      $.ajax("", {
        success: function(data, textStatus, jqXHR) {
         // Do something with the response data
        error: function(jqXHR, textStatus, errorThrown) {
          reject("HTTP request error: " + textStatus + " - " + errorThrown);




  • fix: Always show the selected appointment date, if any, regardless of the print mode


  • feature: New option to retry printing in case of a failure


  • Fix: Special characters in combobox select options are now displayed correctly in the printed PDF document


  • Fix: When a textarea is set to adjust its height automatically to its content, the height is now recalculated once before the form is printed.


  • Fix: Show correct version of the print server when performing a check


  • feature: New option blank form
  • feature: Add special CSS classes to the form.xm-form such as xm-print
  • change: When an element is marked as hidden during print in the form designer (advanced -> Word and PDF export options), the element is now hidden when the print service is used as well. This feature requires at least Xima® Formcycle version 7.0.14.
  • change: Applicable only when print mode is set to dynamic: When an input field did not have a value, its placeholders was shown instead. This was changed so that no value is shown when the input field does not have a value.
  • change: Applicable only when print mode is set to dynamic:  When a select field displayed as a dropdown menu did not have a value, the text Please select was shown instead. This was changed so that no text is shown anymore when the select field does not have a value.


  • Added note regarding $.xutil.onPrint to the plugin UI.


  • Requires at least Xima® Formcycle 7.0.4.
  • change: Note regarding required field is not shown anymore.
  • fix: Show the date format immediately


  • Added a new option for selecting the workflow state used during printing. When no state is selected, the current state of the form record is used as in previous version.
  • Configured user groups are saved correctly.


  • feature: Added a new timeout option that defaults to 30 seconds. When the print service cannot be reached, the workflow may never complete otherwise.


  • fix: The PDF document that was created was not attached to the form record (only for the new workflow action).


  • Adjustments for Xima® Formcycle version 7.



  • Close alert messages when any are opened by JavaScript. Otherwise the print can never finish successfully.


  • Update install scripts for Linux


  • Switch to media type print before printing and wait until no network traffic is ongoing anymore before printing. This helps to show e.g. background graphics from @media print rules.


  • Fix compatibility with Windows service installation script


  • Update puppeteer to latest version, which uses Chromium 108.0.5351.0
  • Add CLI flag  --disableCache=true to disable the browser cache
  • Add CLI flag --isolatedBrowser=true to use a new browser instance for each request.
  • Fix Debian install script, install libgbm1.


  • Update node-windows dependency


  • Update to Chromium 105.0.5173.0
  • Requires at least Node.JS version 14 or higher


  • Fix windows service install / uninstall script (install-windows-service.js and uninstall-windows-service.js)


  • When an error occurs while printing, that error is returned as part of the HTTP response
  • The print server can now be used for printing arbitrary pages / URLs. JavaScript and CSS that must be run in the context of the page to print can be passed as part of the HTTP request.
  • The /pdf endpoint without parameters returns a quick summary of the server status