Changes for page Print-Service-Plugin

From 3.1 to 4.1 From 9.1 to 10.1

From version 4.1

edited by gru
on 02.09.2021, 08:01

Change comment: There is no comment for this version

To version 9.1

edited by awa
on 13.06.2022, 18:29

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.gru
++XWiki.awa

Content

@@ -1,5 +1,9 @@
  [[**Plugin-Download**>>url:https://customer.formcycle.eu/index.php/apps/files/?dir=/FORMCYCLE%20-%20Plugins%20Customer/fc-plugin-print-service&fileid=8194||rel="noopener noreferrer" target="_blank"]] (requires login)
++{{info}}
++{{formcycle/}} Version 7 requires the //Print-Service// plugin version to be **4.0.0** or higher.
++{{/info}}
++
  {{content/}}
  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.
@@ -88,7 +88,7 @@
  Translated with www.DeepL.com/Translator (free version)
--==== Uninstall ====
++=== Uninstall ===
  To uninstall the Print Server, open a command line (cmd) with administrative privileges and execute the following commands:
@@ -110,9 +110,10 @@
  ==== Print-Service Plugin Installation ====
--In order for the plugin to be available in {{formcycle/}} as an action in the workflow processing, it must be deployed in the System Plugin section of the management interface. Instructions for installing plugins can be found [[here>>doc:Formcycle.UserInterface.Client.Plugins.WebHome]].
++In order for the plugin to be available in {{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>>doc:Formcycle.UserInterface.Client.Plugins.WebHome]].
  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
@@ -126,12 +126,20 @@
  For example: {{code language="none"}}http://localhost:8089/pdf{{/code}}
--This completes the setup of the print service plugin and it is available as an action in the [[workflow processing>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing]].
++This completes the setup of the print service plugin and it is available as an action in the [[workflow processing>>doc:Formcycle.Designer.Workflow.WebHome]].
--=== Troubleshooting ===
++== Troubleshooting ==
--==== Command npm install leads to timeout ====
++=== 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: {{info}}C:\Users\{username}\AppData\Roaming\npm;C:\Program Files\nodejs{{/info}}
++* 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:
  {{code language="none"}}
@@ -148,20 +148,18 @@
  More information can also be found here: http://www.fladi.de/2014/02/06/howto-npm-hinter-einem-proxy-verwenden/
--==== Printing does not work ====
++=== Printing does not work ===
  If printing via {{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: {{code language="none"}}http://localhost:<port>/formcycle{{/code}}
--==== PDF is printed, but the message 404 appears ====
++=== 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 ====
++=== Downloading Chromium fails ===
  The following error message appears on the console after running "npm install":
--{{code language="none"}}
--Error: unable to verify the first certificate
--{{/code}}
++{{code language="none"}}Error: unable to verify the first certificate{{/code}}
  The described steps are only a workaround and the environment variables should be set back to the default values after the successful installation!
@@ -174,23 +174,26 @@
  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
  : File name of the created PDF document.
--; **Print mode**
++; 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**
--: Web view: No changes are made to the form and it is converted so that it looks as closely as it does in a web browser as possible.
--; **Zoom factor**
--: Factory by which the form is scaled. Use this to magnify or scale down very large or very small forms.
--; **User groups**
++; 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
++: 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>>Formcycle.FormDesigner.URLParameter]] or access them from within JavaScript.
++; 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>>Formcycle.Designer.Form.URLParameter]] or access them from within JavaScript.
  == CSS-Anpassungen für Druckbild ==
++
  === Input elements ===
--To optimize the form for printing, form elements of type [[input field>>Formcycle.FormDesigner.FormElements.Input]], [[text area>>Formcycle.FormDesigner.FormElements.Textarea]] und [[select>>Formcycle.FormDesigner.FormElements.Selection]] (Drop-Down) may be converted to plain text fields, if the print mode is set to Input elements as text.
++To optimize the form for printing, form elements of type [[input field>>Formcycle.Designer.Form.FormElements.Input]], [[text area>>Formcycle.Designer.Form.FormElements.Textarea]] und [[select>>Formcycle.Designer.Form.FormElements.Selection]] (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:
@@ -223,6 +223,29 @@
  }
  {{/code}}
++=== Avoid page break ===
++
++The default setting for printing is that a page break is inserted after each page of the form:
++
++{{code language="css"}}
++@media print {
++    .CXPage:not(:first-child ), .page-break {
++        display: block !important;
++        page-break-before: always;
++    }
++}
++{{/code}}
++
++In order to avoid breaks, the following rule needs to be defined in the CSS tab of the form:
++
++{{code language="css"}}
++@media print {
++    .CXPage:not(:first-child ) {
++        page-break-before: avoid;
++    }
++}
++{{/code}}
++
  === Usage of other fonts ===
  ==== Technical requirements ====