Generate File
These are process that all generate files.
Last updated
These are process that all generate files.
Last updated
Function
Its function is to generate a Data Matrix (kind of QR code), this can be used to convert text information to a graphical representation matrix of black and white pixels. These are often used for inventory tracking or to hold information about products.
Properties
The properties:
Property Name | Type | Use Description |
---|---|---|
Data input | Expressions, text | Information to convert to matrix. |
Use GS1 standard | Expressions, boolean | Toggle GS1 compliance |
Symbol shape (square or rectangle) | Expressions, text | square of 1 or 4 blocks rectangle of 2 blocks |
Output file | Datalist, file | Field that holds the resulting image. |
For the flowchart, connect from the interaction node to the create data matrix and back to the interaction with the result using the default exit.
One way to use it:
Create a temporary file field that will store the generated image.
Use an interaction node with a button to start the process, an input field and a label for the result.
Put the Data Matrix node in and set the properties.
Create an exit that will go to the node to execute the process.
After executing the process, the temporary field appears, in this case, a file field data type.
The result of the process, with the data matrix generated.
Its function is to generate a Word Document from the contents of a provided WEM Template.
The use of the Word Template property is currently restricted to only Kubernetes environments. This property is for Word template documents to apply preset styling to the generated documents - it is limited, as Word Properties and Fields are not accessible to set using WEM. Also, custom Fonts should be set to be Embedded in the Word File Properties.
This process has the following properties:
Property name | Type | Description |
---|---|---|
Filename | Expressions, text | Set the file name, in the temporary field. |
Word template | Expression, text | You can insert a Word template here. This will be used when the document is created (with limitations). |
Page width | Expressions, number | To set the width of the file in mm. Leave empty for standard A4 |
Page height | Expressions, number | To set the height of the file in mm. Leave empty for standard A4 |
Page margins | Expressions, number | To set the margins of the file in mm. Leave empty for standard A4 |
Page margin left/right | Expressions, number | To set the margin at left or right in mm. Leave empty for standard A4 |
Page margin top/bottom | Expressions, number | To set the margin at top or bottom in mm. Leave empty for standard A4 |
Page as landscape | Expressions, Boolean | To set if page as landscape. Boolean. |
Generated Word Document | Datafield, file | Field to store the generated Word document. |
For the flowchart, connect from the interaction node to generate Word node. As shown below we have the interaction node where we want to activate the process and see the response, and the process node is connected with the button exit and back with the default exit.
One way to use it:
Create a temporary text field that will be the one that receives the document file.
Use an interaction node, then, the Generate Word Document node.
Create an exit that will go to the node to execute the process and use the default exit for the response.
In the node properties, the "edit template" gives access to a template in which you can create what you want to add in the future Word document, this template is similar to the editor that appears inside the interaction node;
Before clicking the generate word button.
as After executing the process, the temporary field appears the one that will carry the result of the executing of the node.
The result.
Its function is to generate a PDF Document through the node configuration. WEM allows, through the templates editor, templates to be converted into a PDF document.
The properties that can be used in the PDF process:
Property name | Type | Description |
---|---|---|
Filename | Expressions, Text | Set the file name, in the temporary field. |
Author | Expressions, Text | To set the author of the file. |
Subject | Expressions, Text | To set the subject of the file. |
Title | Expressions, Text | To set the title of the file. |
Page width | Expressions, Number | To set the width of the file. |
Page height | Expressions, Number | To set the height of the file. |
Page margins | Expressions, Number | To set the margins of the file. |
Page as landscape | Expressions, Boolean | To set if as landscape. Boolean. |
Show header and footer | Expressions, Boolean | To set if show the header and footer. Boolean. |
Custom header text | Expressions, Text | To set the custom header text. |
Custom footer text | Expressions, Text | To set the footer text. |
Show the outline of HTML headers | Expressions, Boolean | To set if you want to show an outline based on the HTML headers (h1, h2, h3) in the document (index with jumplinks). |
Number of levels for the header outline | Expressions, Number | To set the number of levels for the outline (corresponding with html headers h1, h2, h3). |
Generated PDF Document | Datafield, File | Field to store the generated PDF document |
Flowchart
Connect from the interaction node to generate PDF. In the canvas, the process flow that will be executing the project is designed, in the following example, we will be using the start node that will always be by default; an interaction node as shown below, fill in the properties section, where can be set the different dimensions of the future PDF document.
One of the easiest ways to use it basically:
Sample casse an interaction node, then, the Generate PDF document node.
Create a temporary file field that will be the one that receives the PDF file field.
Create an exit that will go to the node to execute the process.
In the node properties, the "edit template" gives access to a template in which you can create what you want to add to future PDF files, this template is similar to the editor that appears inside the interaction node;
Before clicking the generate pdf button.
The result of the process executed.
Its function is to generate a file from text through the interaction node configuration, it is quite interesting and it will help us when we have to make a file that comes from a text type; in a direct and immediate way. You can take text-type fields that contain information loaded in advance, either manually, or with one of the options offered by the import node, through CSV, Excel, JSON, XML, or through an external list of Odata, web service, an API, etc…
Property name | Type | Description |
---|---|---|
File content | Expressions, text | To set the content of the following file. |
Generated filename | Expressions, text | To set the name of the generated file. |
Generated file | Datafield, file | location for the file generated after the process. |
Flowchart
Connect from the interaction node to generate a File from text. In the canvas, the process flow that will be executing the project is designed, in the following example, we will be using the start node that will always be by default; an interaction node as an "overlay", as shown below.
One of the easiest ways to use it basically:
Use an interaction node, then, the Generate file from text.
Create a temporary file field that will be the one that receives the file from text.
Create an exit that will go to the node to execute the process.
Before clicking the button "Generate file from text".
After clicking file from text, the field appears.
The result.
Function
Its function is to generate an image through the interaction node configuration. Generating an image through this process execution node, allows everything that has been developed within an interaction node with its template edition, to be captured in an image which can be customized according to the idea of the user. The most fascinating thing about all this is that it is extremely easy to use and can contribute to many useful processes in systems development.
Properties:
Property name | Type | Use Description |
Filename | Expressions, text | To set the file name. |
Element Selector | Expressions, text | To set the element selector. This allows you to make images for specific preset elements. |
Transparant | Expressions, boolean | To set the transparent of the image. |
Width in pixels | Expressions, number | To set the width of the image. |
Height in pixels | Expressions, number | To set the height of the image. |
Output: Generated image file | Datafield, file | To put the output file field for the image generated. |
One of the easiest ways to use it basically:
Use an interaction node, then we put the generate image node.
Create a temporary text field that will be the one that receives the image file.
Create an exit that will go to the node to execute the process.
In the node properties, the "edit template" gives access to a template in which you can create what you want to add in the future Image file, this template is similar to the editor that appears inside the interaction node;
1. Before clicking the generate pdf button.
2. After executing the process, the temporary field appears.
Functions
Its function is to change generate a generate HTML from a rich text field.
Properties
Property name | Type | Use Description |
File content | Expression, richtext | To set the content in the file |
Generated filename | Expression, text | To set the name of the file generated |
Output: Generated file | Datalfield, file | To put the output file field for the image generated. |
How to use this node?
One of the ways to use this node
The first thing we do is use an interaction node, then we put the generated HTML from the rich text node.
Inside the file content, set the HTML.
After, create a temporary text field which will be the one that receives the generated HTML file.
Create an exit that will go to the node to execute the process.
Before clicking the generate HTML from rich text button.
After executing the process, the temporary field appears.
The result.
With this process node you can generate different kinds of qr-codes, this is an image that can be read by a lot of devices. The process translates a text to a grid of black and white pixels, this can be translated back to text by all kinds of devices with a camera. A lot of times qr-codes are used to share information without having to retype it. This is someting different then a datamatrix which is used in a lot of warehouses management.
Among the properties, it presents:
Property name | Type | Description |
---|---|---|
Data input | Expressions, text | Text input field that is translated to qr code. |
Use GS1 standard | Expressions, boolean | Use GS1 compliant qr codes |
Character set | Expressions, text | Default is UTF-8, the older ISO-8859-1 is also supported and can be used. |
Disable ECI | Expressions, boolean | Extended channel interpretations (ECI) enables using codes longer then standard ISO-8859 and different encodings. default is enabled |
QR version | Expressions, number | Size version of the qr code, more in the blue hint box below. |
Use compact mode | Expressions, boolean | Creates a smaller qr code with less error correction and less readable. |
Error correction | Expressions, text (single symbol) | Level of error correction where:
|
Margin | Expressions, number | Size in pixels of a clear area around a symbol where nothing is printed. |
Output: Output file | Datalist, file | The location where the output should be stored. |
The symbol versions of QR Code range from Version 1 to Version 40. Each version has a different module configuration or number of modules. (The module refers to the black and white dots that make up QR Code.) "Module configuration" refers to the number of modules contained in a symbol, commencing with Version 1 (21 × 21 modules) up to Version 40 (177 × 177 modules). Each higher version number comprises 4 additional modules per side. More about that here.
One of the easiest ways to use it is shown below, we start with a interaction node, here we provide the input for the qr code and set up a few of the options. The interaction node has a exit to the qr process node, and uses the default exit to go back and show the result.
1. The first thing we do is use an interaction node, and a field to store the code that is made. In this case is that a transient or session field where we temporary store the image.
2. You can leave all the settings on default by keeping them empty or add values to them. In the images below you will see that there are a few transient fields added for specific settings.
3. Add a button that triggers the node exit Create QR-code thats connected to the process node. and add the field that you used for the output to the interaction template.
Fill in the input field with the code you want to convert.
select the create code button that invokes the process
The result of the process, with the QR-code generated.
Its function to create a ZIP archive.
Among the properties, it presents:
Property Name | Type | Description |
---|---|---|
Input file | Expressions, File | The datafield where the file you want ZIPed is saved. |
Output file name | Expressions, text | Name of the ZIP File |
Output file | Datafield, file | Location of where the ZIP is saved. |
One of the easiest ways to use it basically
The first thing we do is use an interaction node, then we put the generate Generate Zip Archive.
Create a temporary text field that will be the one that receives the Generate Zip Archive.
Create an exit that will go to the node to execute the process and back again to show the result.
You have created a ZIP packager, this can be used when working with large files you want to save in the datamodel.
After executing the process, the temporary field appears.
The result: