All Collections
Advanced App Building
Horizontal Sections with Advanced Table
Horizontal Sections with Advanced Table

This article will help you understand how and why to use the Advanced Tabled feature.

Rosco Pettinari avatar
Written by Rosco Pettinari
Updated over a week ago

While building a WORKFLOW you have four different types of SECTIONS:
1. Vertical sections: That you will use when you want to stack your elements one on top of each other.
2. Trigger sections: That will work exactly the same as Vertical sections, but will be hidden by default and will only show up depending on a customizable scenario.

3. Approval section: That you will only use when ADVANCED WORKFLOW is active.

4. and Horizontal section: That you will use when you want your elements as TABLE COLUMNS.

A Standard HORIZONTAL SECTION will have all its elements as columns and users will interact with it by adding, editing, or removing rows. But in some scenarios, you might not want users to ADD rows. Or maybe you want to allow them to ADD rows, but not to DELETE them (or also not even EDIT them).

For example, let's pretend that we are building a maintenance WORKFLOW where there is a section where we need the users to indicate if Batteries A, B, and C are charged and in good condition. In our paper-based form, these could look something like this:

In this case, we don't want the user adding an extra row, we just want them to answer YES or NO on those two questions for each battery. And also, we don't want them to EDIT the names of the batteries.

In order to build this exact scenario with FAT FINGER, you will add a HORIZONTAL SECTION that will look like this:

As you might notice, every HORIZONTAL SECTION has an ADVANCED tab, if you click it, you will see the following:

By default, this feature is not enabled. This means that the first thing you should do is to enable it.

Enabling ADVANCED TABLE will activate this interface from where you can set your preferences. Each switch applies to ROWS, you can decide if users will be able (or not) to EDIT, ADD, and DELETE. In the example we are building, we want users to EDIT the rows (to answer if the batteries are charged and in good conditions), but we don't want them ADDING or DELETING rows just to be sure that the end result will be exactly the same as in our paper-based form (a table with those three rows).

The next step will be to add those three rows and also LOCK the column that we don't want the user to EDIT. Activating the lock on a column means that the column will become a READ-ONLY element. Of course, each cell of the ADVANCED TABLE will give you the option to set a default value (like "Battery A", "Battery B", and "Battery C").

The end result will be this: A HORIZONTAL SECTION with three rows where the user will only be able to EDIT the rows (but not to DELETE them or ADD new ones).

And as you can see, when you edit each row, the first element is READ-ONLY, which means that the user will not be able to EDIT where it says "Battery B". But they will most certainly be able to answer YES or NO to those two questions.

Did this answer your question?