Ideas: More dependencies and Operations

Hello @digiblogger

All the features described can be implemented with the calculated fields.

For example, the slider. If you leave empty the “Field Caption” attribute in the slider’s settings (assuming it is the fieldname1) and insert just below this field a calculated field, with the equation:

(function(){
switch(fieldname1)
{
case 1: return 'bad';
case 2: return 'boring';
case 3: return 'ok';
case 4: return 'great';
case 5: return 'amazing';
}
})()

You would have the same result. Even, if you want make the integration more organic, you can assign to the calculated field a custom class name, for example: my-slider-caption

and define this class as follows (through the “Customize Form Design” attribute in the “Form Settings” tab):

#fbuilder .my-slider-caption label{display: none !important;}
#fbuilder .my-slider-caption input{border: 0 !important;background: transparent !important;}

For the other cases, the process can be implemented through the equations too, some of them with a little more of effort, but other is simply to call an operation. For example, if you want to assign the value: 20 to the fieldname123 field through an equation associated to a calculated field, the code would be as simple as:

getField(123).setVal(20);

More information in the following link:

https://cff.dwbooster.com/documentation#managing-fields-module

Best regards.

Hello @digiblogger

It has been a pleasure.

Best regards.