The Append to zip archive is an advanced utilities workflow component, that appends the payload to a zip file. The zip file will be created, if the referenced zip file does not exist.
The first time you add to a zip archive, the archive is initialized and opened for writing. You can use this append component multiple times to add more files to the same archive. The actual archive exists as a property of the workflow while you are adding to it. When you are done adding to the archive, you can use the component "Zip to payload" to close the zip archive and move it to the payload. Finally you might want to send or save the zip file e.g. with the UNREGISTERED EVALUATION VERSION component.
The parameters are:
Zip ID
An identifier of the zip archive. If you want to create multiple different archives in the same workflow, you can do so by giving them different IDs. If you only want to create one zip file, then just leave this at the default value.
Output filename
The file name that you want the current payload to have within the zip archive.
Folder within zip
Optional folder path within the zip archive, for the folder in which to place the payload.
Related workflow components:
This component is an advanced utilities component.
The component has these parameters:
Attachment name
The name of the workflow attachment, that is to be extracted and converted into the payload
Output type
The file type of the attachment. This affects the possible selection of components for the next action in the workflow.
The base64 XML node to payload workflow component has these parameters:
XPath expression
The path to where the resource is stored (Base64 encoded) in the XML payload.
Input type
The type of resource, that is extracted from the XML file.
This workflow component deletes a resource from the Library.
Related workflow components are: List resources, Resource to payload, Resource to attachment and Save in resources.
An example of how this can be used with the List resources can be found in this section.
The Delete resource workflow component has this parameter:
The path in the Library to the resource including the resource name. The first folder in the path is the resource type.
The folder for the resources are:
Resource | Path | Example |
---|---|---|
Components | /templateComponent | /templateComponent/Common/Footer.icmp |
Documents | /document | /document/Demo/Demo_Invoice.xml |
Fonts | /font | /font/arial.ttf |
Images | /image | /image/Demo/Leif1.jpg |
Mail templates | /mailTemplate | /mailTemplate/defaultMailTemplate.vm |
Other | /other | /other/Certificates/MOCES_gyldig.p12 |
Styles | /style | /style/header.style |
Templates | /template | /template/Demo/InvoiceDemo.ift |
Transforms | /transform | /transform/production/copyNode.xsl |
Translations | /translation | /translation/Demo/translate.properties |
Validation rules | /validationRule | /validationRule/Training/Validate_demo_xml.xsd |
Workflow | /workflow | /workflow/KSE_test.wf |
This component takes a PDF as input payload and returns a signed version of that PDF as output.
This component can be used to sign a PDF document using the DigitalSign service called "Certificado Qualificado - Selo EletrĂ³nico Cloud" (in portuguese).
This functionality is required for digitally signing invoices in Portugal.
Please note, that this component can only be called, if the workflow payload is PDF, so a normal use is to insert this component after the Create PDF document component, as this component generate a PDF and keep it in the payload only.
The advanced utility component has these parameters:
DigitalSign HSM Cloud settings
The name of the server settings to use. This is setup in the tenant settings here.
Authorizer's TOTP Id
The authorizer's id, which also acts as a reference to the certificate chain.
TOTP Secret
The shared secret for the TOTP Id, which should be used to generate a time-based one-time password.
Document alias
A name for the document. This does not need to be unique.
Location
The signer's location at the time of signing.
Signing resons
The reason for signing the document.
Note that the certificate chain that is used for signing the document, will be retrieved from the DigitalSign service based on the TOTP Id.
The advanced, utilities component, Edit document text is used in combination with the Webforms module.
One prerequisite for this component is, that you have already setup a template with one or multiple editable text elements.
This workflow component activates the webform (template) and prompts the user for the value of each of the editable text elements. The workflow will wait for the user and not proceed until the web form has been filled out.
You should NOT combine the Edit document text component with a split or a multicast, which spawns multiple threads.
The edit document text workflow component has these parameters:
Edit flow unique name
This is directly linked with the web page, that is hosted by InterFormNG2 in order to allow the user to enter the values of the editable texts.
The default value is Standard, which means that the web page will be: https://localhost:8086/forms/tasks/?id=edt%25Standard, where localhost of course should be exchanged for the IP-address or host name of the InterFormNG2 server and the port number 8086 should replaced with the port number used by InterFormNG2, if this has been configured to another number.
Template
This is the name of the template, that contains the editable texts and the template, that is also used for the final output.
Description
This value is shown on the web page, so this can be used by the user to identify the right web form to fill out, where this page looks like this: