Consistent approach for built-in functions (or expression builder)
It is somewhat difficult as a new iformbuilder user to have a full understanding of the functions that are available in forms and how they work. It would be nice to have a comprehensive way that things are implemented, for example that every field would have a representative "toString" or "getValue" method and some elements would have additional methods, such as showing the "key" for the option list selection.
It seems like these are implemented in different manners: i.e. ZC DisplayValue vs using the element_name in an option list to get the key. It would make more sense to use element_name.tostring vs element_name.getkey. Going even further, it might make sense to force the user to refer to the form: i.e. this_form.element_name.getkey that way you could easily refer to the parent form if need be: i.e. this_form.parent.element_name.getValue.
It could also be helpful to build an "Expression Builder" with some of the built-in functionality exposed in a more visible manner to the end user.
-
Hey Roland. This would be a great addition. This would certainly cut down on errors in building and allow writing faster more accurate javascript if you have this at your fingertips. Our current reporting offering has a function builder. Take a look at this screenshot. https://drive.google.com/file/d/1m7Y0s_AzFRzWcaE7kou19XLxN-GeVEn9/view?usp=sharing
Please sign in to leave a comment.
Comments
1 comment