Page History
...
Name | Description | Direction | Type | Required | Example |
---|---|---|---|---|---|
Document | The name of the document as it is stored in studio. | Input | Document | False1 | Application |
Page | The name of the page as it is stored in studio. | Input | Page | False1 | - |
FileName | The schema to generate a file name. | Input | Expression | True | "Application " + TODAY + ".pdf" |
FileType | The file type that is to be generated. | Input | String | True | pdf (specify without quotes) |
Connection | The connection2 on which the generated file should be stored. | Input | String | True | onfilesystem |
Persistence | Store a generated document temporary or permanently. | Input | Domain | True | Permanent |
CreateInstance | Create a new instance. | Input | Boolean | True | Yes |
Relation | The newly created instance will be linked to the given relation. | Input | Relation | False | Applications.RelApplication |
UpdateFileID | The file id that should be overwritten. | Input | Attribute | False | - |
FileID | The attribute that contains the file id. | Output | Attribute | True | Document.Id |
AuthorizedRoles | Select roles that are authorized for this document | Input | Role(s) | False | Junior, Senior |
CaseId | The id of the case where the document is generated for3 When using the Process-Engine the value of this field is set as process_id in the metadata When using the Case-Engine, this field must be omitted. It will automatically be filled with the caseId during task execution. | Input | Expression | False | Control.CaseId |
...
Overview
Content Tools