You describe where the data is stored.
As for paths, here are example coordinates entered:
first look - do not enter last ;
your data shoul be
It is very interesting.
One more question.
As I understand, you describe somewhere your table (and fields), and after that you construct where clause (it is on image). And where you define what columns (lat and lng) or column (pair) will be used for placemarks or paths? And where definition for data type to display (placemark or path)? Where you define what popup content will be?
You select column names (it is called "Pole" in our example) and specify where clauses.
You can define the column with coordinates in different ways. Here a separate "element" - column containing coordinates is added to the table. But you can as well have a separate page where you specify which column is name, which column should be the popup, etc. Actually you have it in your software, as you specify which kml variable to use in the popup, so it is quite the same.
Or simply force user to use column with names like "Latitude" or "Coordinates". Fabrik has a separate "column" that can be added to any table, where you place the coordinates in a fixed format, and that is how it works.
Whether the result should be displayed as path or points, is another thing. This is done in the visualization further on (in case of Fabrik it is the googlemap visualization.