Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.tkr
	1	+XWiki.nlo

Default language

...	...	@@ -1,0 +1,1 @@
	1	+de

Content

...	...	@@ -1,42 +1,39 @@
	1	+{{version major="6" minor="2" patch="0"}} This feature is available since {{formcycle/}} version 6.2.{{/version}}
	2	+
1	1	{{content/}}
2	2
	5	+{{figure image="myforms_export_blank_en.png" clear="h1"}}
	6	+The Word and PDF export lets you create a blank form. It can be printed and filled out manually.
	7	+{{/figure}}
	8	+
3	3	== Function ==
4	4
5		-This feature can create a Word or PDF document from a form. Word documents created from this feature can be used for the action Word-Fill in the forms' workflow. The export file can be saved as a form ressource.
	11	+This feature allows you to export a {{formcycle/}} form into a PDF or word document. Word documents created by this feature contain placeholders and can be used directly with the workflow action [[Word Fill>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.Actions.WordFill.WebHome]]. You can also saved the exported file as a form ressource.
6	6
7		-The selection form elements contained in the export can be made in [[{{designer/}}>>path:/xwiki/bin/view/Formcycle/FormDesigner/]] for each form element individually.
	13	+For each element, you can [[choose whether it should be included in the form export>>doc:Formcycle.FormDesigner.ElementProperties.PrintExport]] in the advanced settings panel of the {{designer/}}.
8	8
9	9	== Options ==
10	10
11	11	=== Form export ===
12	12
13		-This option allows downloading and instant viewing of the form export.
	19	+These options let you customize the form export:
14	14
15		-==== Format ====
	21	+; Format
	22	+: You can choose one of .pdf, .doc (old Word format) and.docx (new Word format).
	23	+; Language
	24	+: Selection of the language in which the form should be exported.
	25	+; Export template
	26	+: By default, no template is used and exported file contains only the exported form. You can specify a template to insert the exported form into an existing document. For example, you could use a template to include a header page or to insert a header or footer. The exported form is appended to the end of the template document. To include the exported form at another position, you can use placeholder //INSERT_FORM//. This placeholder needs to be inserted as a form control element, see the [[Word Fill>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.Actions.WordFill.PreparationWord]] action for details.
	27	+; Use visible form placeholders {{version major="6" minor="4" patch="0"/}}
	28	+: The form variables are used as element names (bookmarks) in the form elements of the Word file and are visible. Without this option, the placeholders are stored as help text. Input elements are then not visible in the Word document. (//Only works in Word documents//)
16	16
17		-You can choose from .pdf, .doc and.docx
18		-
19		-==== Language ====
20		-
21		-Selection of the language in which the from should be exported.
22		-
23		-==== Template ====
24		-
25		-As a default, no template is used and the form export will be made in a new file. If you want to include the export in a specific, existing document, choose this as a template. The source of the template (client or form ressources) has to be chosen first. Then, the specific file can be selected. If nothing is configured further, the form export will be added to the end of the template document. The exact position of the form export can be configured by using the placeholder variable //INSERT_FORM //.
26		-
27		-
28	28	=== Further processing ===
29	29
30		-By using this option, the form export can be processed internally by saving it as a form resource.
	32	+This option lets you save the exported form as a form file. You can then use the form file in workflow actions.
31	31
32		-==== Save as form resource ====
33		-
34		-Needs to be activated, if this option is requested. .
35		-
36		-==== File name ====
37		-
38		-Name of the file that will be created
39		-
40		-==== Override existing resource ====
41		-
42		-Determines if existing form resources with the same name should be overridden or not. If not activated and a file with the same name is present in form resources, this export file name will be extended to allow unique form resource file names.
	34	+; Save as form file
	35	+: If enabled, the exported blank form is saved as a form file.
	36	+; File name
	37	+: Name of the file that is created.
	38	+; Override existing resource
	39	+: If a file with the same name exists already: When this option is activated, the existing file is overridden. Otherwise, when this option is disabled, the new file is renamed.