You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Camunda Assistant GPT suggested that one can create a custom function in JS, that is made available to the FEEL engine within a form-js form.
I'd like to test this out with a toSentence function that would replace the complex/ugly code we currently have to transform the benefit names and eligibility checks from camel case to a more readable format. (used in the "Results" section of the form)
The text was updated successfully, but these errors were encountered:
With some more research, it looks like the only way to do this that would make the custom function usable when building/previewing the form is to fork the form-js repo.
I will take another look at the docs to see if I missed anything, otherwise I don’t know if the complexity is worth the time right now.
Letting this go for the moment, since having a toSentence function available in the form is the only compelling use case at the moment, and we already have a working (if clunky) solution for that.
The Camunda Assistant GPT suggested that one can create a custom function in JS, that is made available to the FEEL engine within a form-js form.
I'd like to test this out with a
toSentence
function that would replace the complex/ugly code we currently have to transform the benefit names and eligibility checks from camel case to a more readable format. (used in the "Results" section of the form)The text was updated successfully, but these errors were encountered: