Wiki source code of PDF-Datei befüllen


Hide last authors
Nils Schweigert 19.1 1 {{figure image="pdf_fill_en.png" width="400" clear="h1"}}
2 Configuration interface of the action //Fill PDF document//
XIMA Admin 1.1 3 {{/figure}}
4
Nils Schweigert 19.1 5 The action //Fill PDF document// allows to fill an existing PDF form with the transferred form data.
XIMA Admin 1.1 6
Nils Schweigert 19.1 7 The PDF must be prepared accordingly for this, see the section [[Prerequisite of the PDF form to be filled>>doc:Formcycle.Designer.Workflow.Actions.FillPdfDocument.PreparationPDF]].
XIMA Admin 1.1 8
Nils Schweigert 19.1 9 Alternatively, the [[PDF Import Tool>>Formcycle.Designer.Form.PdfImport]] provides the ability to upload a PDF document and create the necessary actions automatically.
XIMA Admin 1.1 10
Nils Schweigert 19.1 11 == Parameters ==
jdr 13.2 12
Nils Schweigert 19.1 13 === Details for PDF filling ===
jdr 13.2 14
Nils Schweigert 19.1 15 ; File
16 : Selection of the PDF template to be used. Available are [[Formcycle.UserInterface.MyForms.Files]], [[Client Files>>doc:Formcycle.UserInterface.FilesAndTemplates.Files]], files loaded via a URL (external resource) or process attachments. See [[actions>>doc:Formcycle.Designer.Workflow.Actions.WebHome]] for a list of supported URL protocols.
17 ; Resource URL
18 : Enter the URL to be retrieved if //External Resource URL// is selected as file.
19 ; File name for search
20 : If //Find process attachments by filename// is selected as file, the filename for searching can be selected here.
21 ; Type filter
22 : This filter can be used to narrow down the search of the process attachments.
23 ; Font for text fields
24 : Selection of the font to be used for filling the PDF fields. Available are the fonts that are available on the server.
jdr 13.2 25
Nils Schweigert 19.1 26 === Storage options for the created files ===
jdr 13.2 27
Nils Schweigert 19.1 28 ; Output file name
29 : Name of the output file.
30 ; Attach file to form record
31 : If this option is selected, files created in this action will be attached to the form record. Otherwise, they are only available for other actions within the workflow processing in the same processing chain.
jdr 9.3 32
Nils Schweigert 19.1 33 == Action variables ==
jdr 9.3 34
Nils Schweigert 19.1 35 Actions of type //Move to inbox// provide [[Action variables>>Formcycle.UserInterface.Variables||anchor="HActionvariables"]] which can be used in subsequent actions.
jdr 9.3 36
Nils Schweigert 19.1 37 === Standard action variables ===
jdr 9.3 38
Nils Schweigert 19.1 39 ; [%$<action name>.SUCCESS%]
40 : Return whether action was successfully executed. Returns Boolean (true/false).
41 ; [%$<action name>.RESULT%]
42 : Return all results provided by the action in structured form.
jdr 9.3 43
Nils Schweigert 19.1 44 ; [%$<action name>.ERROR_CODE%]
45 : The error code thrown in case of an error in the action. Empty if no error occurred.
46 ; [%$<action name>.ERROR_MESSAGE%]
47 : The thrown error message in the action's error case. Empty if no error occurred.
jdr 9.3 48
Nils Schweigert 19.1 49 === Action specific action variables ===
jdr 9.3 50
Nils Schweigert 19.1 51 ; [%$<action name>.RESULT.fileSize%]
52 : Size of the created PDF file, in bytes.
53 ; [%$<action name>.ERROR.message%]
54 : Error message returned if the PDF file could not be written to the file system, the specified URL does not match a valid format, no source file could be determined, or the file format of the source file is not supported.
jdr 9.3 55
XIMA Admin 1.1 56 == Videos ==
57
Nils Schweigert 19.1 58 [[Workshop-Video>>doc:Workshops.052020 PDF Print, PDF Fill, PDF-A und PDF Merge.WebHome]]