Changes for page Print-Service-Plugin


From version 4.6
edited by gru
on 02.09.2021, 08:10
Change comment: There is no comment for this version
To version 10.1
edited by awa
on 14.06.2022, 13:52
Change comment: Add changelog

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.gru
1 +XWiki.awa
Content
... ... @@ -92,7 +92,7 @@
92 92  
93 93  Translated with www.DeepL.com/Translator (free version)
94 94  
95 -==== Uninstall ====
95 +=== Uninstall ===
96 96  
97 97  To uninstall the Print Server, open a command line (cmd) with administrative privileges and execute the following commands:
98 98  
... ... @@ -117,6 +117,7 @@
117 117  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]].
118 118  
119 119  If the old version of the print service plugin (phantom plugin) was already installed, the following procedure is recommended for installation:
120 +
120 120  * Disable the phantom plugin
121 121  * Delete the phantom plugin
122 122  * Upload new print service plugin
... ... @@ -132,10 +132,18 @@
132 132  
133 133  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]].
134 134  
135 -=== Troubleshooting ===
136 +== Troubleshooting ==
136 136  
137 -==== Command npm install leads to timeout ====
138 +=== Command npm not found ===
138 138  
140 +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:
141 +
142 +* Call up the environment variables via Control Panel > System > Advanced System Settings > Environment Variables button.
143 +* In Path you should find the following entries: {{info}}C:\Users\{username}\AppData\Roaming\npm;C:\Program Files\nodejs{{/info}}
144 +* Confirm everything with Ok. The console then be opened again with admin rights.
145 +
146 +=== Command npm install leads to timeout ===
147 +
139 139  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:
140 140  
141 141  {{code language="none"}}
... ... @@ -152,20 +152,18 @@
152 152  
153 153  More information can also be found here: http://www.fladi.de/2014/02/06/howto-npm-hinter-einem-proxy-verwenden/
154 154  
155 -==== Printing does not work ====
164 +=== Printing does not work ===
156 156  
157 157  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}}
158 158  
159 -==== PDF is printed, but the message 404 appears ====
168 +=== PDF is printed, but the message 404 appears ===
160 160  
161 161  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.
162 162  
163 -==== Downloading Chromium fails ====
172 +=== Downloading Chromium fails ===
164 164  
165 165  The following error message appears on the console after running "npm install":
166 -{{code language="none"}}
167 -Error: unable to verify the first certificate
168 -{{/code}}
175 +{{code language="none"}}Error: unable to verify the first certificate{{/code}}
169 169  
170 170  The described steps are only a workaround and the environment variables should be set back to the default values after the successful installation!
171 171  
... ... @@ -178,20 +178,23 @@
178 178  
179 179  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:
180 180  
181 -; **File name**
188 +; File name
182 182  : File name of the created PDF document.
183 -; **Print mode**
190 +; Print mode
184 184  : Input elements as text: Input elements are converted into plain text fields and the form is adapted to the width of the page.
185 -; **Print mode**
186 -: 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.
187 -; **Zoom factor**
188 -: Factory by which the form is scaled. Use this to magnify or scale down very large or very small forms.
189 -; **User groups**
192 +; Print mode
193 +: 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.
194 +; Zoom factor
195 +: Scale factor for the form. Use this to magnify or scale down very large or very small forms.
196 +; Blank form
197 +: 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.
198 +; User groups
190 190  : 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.
191 -; **URL parameter**
200 +; URL parameter
192 192  : 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.
193 193  
194 194  == CSS-Anpassungen für Druckbild ==
204 +
195 195  === Input elements ===
196 196  
197 197  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.
... ... @@ -227,6 +227,29 @@
227 227  }
228 228  {{/code}}
229 229  
240 +=== Avoid page break ===
241 +
242 +The default setting for printing is that a page break is inserted after each page of the form:
243 +
244 +{{code language="css"}}
245 +@media print {
246 + .CXPage:not(:first-child ), .page-break {
247 + display: block !important;
248 + page-break-before: always;
249 + }
250 +}
251 +{{/code}}
252 +
253 +In order to avoid breaks, the following rule needs to be defined in the CSS tab of the form:
254 +
255 +{{code language="css"}}
256 +@media print {
257 + .CXPage:not(:first-child ) {
258 + page-break-before: avoid;
259 + }
260 +}
261 +{{/code}}
262 +
230 230  === Usage of other fonts ===
231 231  
232 232  ==== Technical requirements ====
... ... @@ -256,3 +256,40 @@
256 256  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.
257 257  
258 258  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.
292 +
293 +== Changelog
294 +
295 +=== 4.2.0
296 +
297 +* feature: New option //blank form//
298 +* 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 {{formcycle/}} version 7.0.14.
299 +* 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.
300 +* 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.
301 +
302 +=== 4.1.2
303 +
304 +* Added note regarding //$.xutil.onPrint// to the plugin UI.
305 +
306 +=== 4.1.1
307 +
308 +* Requires at least {{formcycle/}} 7.0.4.
309 +* change: Note regarding required field is not shown anymore.
310 +* fix: Show the date format immediately
311 +
312 +=== 4.1.0
313 +
314 +* 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.
315 +* Configured user groups are saved correctly.
316 +
317 +=== 4.0.2
318 +
319 +* feature: Added a new timeout option that defaults to 30 seconds. When the print service cannot be reached, the workflow may never complete otherwise.
320 +
321 +=== 4.0.1
322 +
323 +* fix: The PDF document tha was created was not attached to the form record (only for the new workflow action).
324 +
325 +=== 4.0.0
326 +
327 +* Adjustments for {{formcycle/}} version 7.
328 +