Platform update for 2019-11-28


We've released a new update for Tabbli platform (version 0.9.2) with a lot of improvements. Happy to present new features:

  • Computed "Name" properties
  • Upgraded reverse relation user interfaces with easier creation of related records
  • Action buttons
  • Highly improved automation scenarios

And a lot of bug fixes, performance, and stability improvements.

Let's deep into details.

Computed "Name" properties

Not every data structure needs a name (or other unique string which describes a record). This property is required by default because it uses in list views and many other user interfaces where we need to show a record. In the next picture, you can see an example when manually filled names might sense.

But for other kinds of records, such property is using only for information purposes and could be generated automatically. Look at the next image, here Name is a concatenation of two other properties: Class and Topic.

In some cases, the amount of such data could be huge and manual filling is tending to errors and is very time-consuming. Now, it could be fixed easily with new computational options for the Name property.

There you can use a template like this:

{%  if and  %}{{}}. {{}}{%  endif  %}

Take a look at "@LANG" directive in the template. It is using for replacing the language code. Because Name property is multilingual the template applies for each language. The corresponding syntax allows using proper name translations for the creation of the result. Additional "if" clause is using to check the availability of translations. After that changes the "Name" property will be disappeared from the record forms:

Improved reverse relation interfaces

All reverse relations interfaces now show a full list of related records with pagination support. Also, you can use the particular "New" button for the easy creation of the related record. The particular relation will be initialized automatically.

Action buttons

Now you can add custom buttons to the record or collection interface. For the current moment, we are supporting two types of such buttons:

  • Go to URL
  • Run scenario

For setting up the buttons you can use the new item in Options menu:

There are a lot of use cases you can cover with this new feature. For example, if you have records which have particular public pages it is useful to create a button for preview (like in our own blog structure, for example):

The new button is visible in the interface like that:

Automation scenarios improvement

Now you can use DB() object inside scenario expressions. It allows doing a lot of transformations with database data. And also, it allows creating new records. So, you can use scenarios for automatically creation of the new records. If you need to launch the scenario only with pressing by a button (not like a reaction on some triggering event) you can select "None" as a trigger. After that, you can add an action button for launching it.

Here, at the diagram, you can see that the scenario gets some data from the database and then starts a loop by adding new records to the database automatically.