Generating Files Inside Business Apps
You can easily add file block inside your business app by dragging and dropping the following: 
You will see the following inside your diagram:
You can set your block's name and its icon by configuring the following:
Uploading Template File
You can easily upload a template by using the following:
Your file will appear in the dialogue below once it gets uploaded:
The system will detect your fields and display them as shown below:
You can start clicking on each field to set their dynamic data configuration. You will see the following screen:
In case you have previous blocks which contain data, which can be inserted, the screen will also contain those blocks:
You can drag-and-drop previous blocks, and select the data from them that you would wish to insert. In the example below we are selecting a previous block 'Form' (as shown above) inside the editor:
In our case, since we've dropped a data input form block, it provides with the forms fields for us to select the right one:
If we press the checkbox next to the 'Client Name' field, we will have that particular field inside the editor:
This means we will have the dynamic field inserted here during the execution, and it will end up inside the email message body. You can also insert time, date, and date with time by dragging and dropping either of the following blocks:
You can format your date/time as shown below:
Drag-and-drop the user block: 
You will get the following dialog, containing users from your organization:
If you select 'During runtime insert user that executes this', then the system will insert whoever will be executing this business app. Otherwise, you can select a specific user. When dealing with end-users, you can specify which data you would like to be inserted into your email message body. You can for instance tick name, title, and the phone number. In case you have selected multiple data fields, at the bottom you have 2 more checkboxes, which specify how you would like to separate those fields. The first one allows separating the fields with a comma, while the second option allows separating your data fields with a new line.
If you are happy with your settings, click the 'Apply and Close' button:
If you would like to remove the field you've just selected, simply click on the X button:
Alternatively, you can press the 'Clear' button at the bottom of the dialogue: 
File Title
The following will allow setting the file title during run-time:
Description
Your file can have a description in the following field:
Display
You can display the file your app is generating during run-time by enabling the following option:
You might need to enable this when a contract file is being generated, for instance, and the end-user needs to see it while executing the business app.
Post It?
You can also post the newly generated file to end user's timeline. This is useful when resources need to be shared for others to see.
Delete the Previous Version?
You can delete previously generated files by your business app enabling the following option:
This is useful if your business app is generating a contract file, and you want to only have one contract file at any time, regardless of how many times it gets generated. Otherwise, keep this option 'off'.
Replace Files?
In case you do not wish to keep the previous version of the file, enable the following option and the app will ensure that the previously generated version is replaced with the new one:
Document Type
You can generate either MS Word and/or PDF type of documents by selecting the following:
Notify Users
When the file gets generated, you can notify users about that. To set it up, simply start typing in a person's name and select your person from the list.
User Signature
Each end user can save their signature in their profile, which can then be used to generate documents – such as automatically signing contracts and saving the signed files in PDF or Word formats. To configure end user signatures, click the menu option below:
You can add or remove end user signatures in the section below.
To add a user signature, simply select the field in your document where you want the signature to appear.
Choose the Signature option. You can do this for a specific user or for the user running the no-code app. This selection is determined by the user block, which you can easily drag and drop into the editor.
Create Barcodes
To add a barcode, just select the field in your document where you want it to appear.
You can then drag and drop a data field from a previous block, or if your barcode value is static, simply type it in.
To choose your barcode type, simply select one from the list.
Here are some other options you can customize:
- Set the height of your barcode in pixels.
- Adjust the width of the thick bar.
- Customize the width of the thin bar.
- Choose your preferred font size for the barcode.
Additionally, you can explore other options, including:
- Adding a border around the barcode.
- Displaying text below the barcode.
- Stretching the text for better visibility.
- Showing or including a checksum.
Feel free to adjust all the necessary settings or leave them as default based on your document needs!
Create QR Codes
To add a QR code, select the field in your document where you’d like it to appear.
You can either drag and drop a data field from a previous block or, if your QR code value is static, just type it in directly.
You can also adjust the height and width of your QR code.
Merge Documents
If you've created multiple documents (like various contract pages or invoices) in your no-code app and want to merge them into a single document, just select the option below:
Sending Resources from No-Code Apps
Inside the no-code app editor, almost any resource can be sent to a Kanban board, or Saved Resources board.
The platform will atomatically send a resource to the Kanban board or Saved Resources board when this option is enabled.
Aggregating Values in No-Code Apps
We can easily aggregate database table fields to get results like the sum, minimum, maximum, count, and average (SUM, MIN, MAX, COUNT, AVG). To do this, you’ll need a data access block and a calculation block.
In the formula editor of the calculation block, simply drag and drop your data access block, select the field you want, and then choose the desired operation – like SUM or AVG – from the options provided, as shown below.
In the example above, during runtime, the system will calculate the total of all price fields from the available records and display that sum in the calculation block as the result. You can use this result in a variety of ways. For instance, you can include it in the body of an email, add it to your PDF invoice, save it to another table, or even send it to another system using a REST API. Just a quick reminder: all operations, except for counting, should be performed with numeric data only.
Inserting Tables into Documents
We often find ourselves swimming in data, especially when it comes to tasks like creating customer invoices or delivery notes. One of the main features of these documents is the table that lists the purchased items. What’s interesting is that this table isn’t always the same. Some days, we might only need to include two items, while other times, we could be looking at a list of twenty or more.
When you add a data access element with multiple rows to your document and include fields in a table, the system automatically generates the right number of rows, up to a maximum of 1,000 to keep things running smoothly. It then fills those rows with data from your access element, making it easy to show all the necessary information without any extra hassle.
For instance, in the Word document, we’ve set up a table that features different data tags:
Our data source will include the following records:
We will connect it to the document records within the table. The name will be linked to Value_A, the email address field will connect to Value_B, and the price will be associated with Value_C.
When you run the app, the system automatically fills the table by adding the necessary number of rows (up to a maximum of 1,000). Here’s what the generated table looks like:
Accessing Data From Two or More Data Sources
In the following example, we have three data elements corresponding to three different table columns.
However, the data will come from 2 different data sources: Access and Access (1)
The first data source contains the following records:
The second data source includes four rows:
During runtime the system will merge 2 data sources into 1 table. That means it will simply place both data sources into the rows in default order, producing the following:
In real-life situations, you would typically link both tables when accessing them – such as through a primary and foreign key relationship – or you might create a separate table with the linked data before including it in your document.
Was this article helpful?