Folks,
Got one that I just keep running into a wall on. I have several "form" fields and I can control them (show/hide and enable/disable) using the structure FPMGB_S_LISTFIELD_DESCR and assigning a related "technical" field for my form field.....I can then set/flag the "technical field" which will then affect the corresponding form field as I like (basically like binding the "visible" property of my form field to the dynamic value of another field).
My problem is that for buttons....I cannot find any kind of similar "hook". Within my own class (not feeder), I can define a handler for "FPM events" and can capture that (so I do know what/when a button is pressed/clicked)....but even then, it is just a listener and cannot control the button(s) itself. However, because I set up "technical" fields related to my "form" fields, I can set/unset those technical fields as I like (dynamic) and it will immediately control the related fields. Works great!....even down to the cell level on tables!!!
A good example is on a pay related form we use. We have form field that shows to help calculate a salary on either % change or amount they would like to get too. There is a button they press to then make the calculations and distribute it over wage types correctly to come up with that salary. Now, for countries that do not use "annual salary", we simply hide the "calculation" form input box....works great....but the button is still there. For now, if the user just presses the button, we do at least give them a message that annual salary does not apply to their country and to disregard...but that is a "kludgy" way to handle it. Would be nice to hide the button too (like the form field).
Is there anyways to get a "hook"/handle to a button within my FPM configuration at runtime and control it as I like? I cannot modify the "feeder" as it is used among several apps/configurations, so I am hoping there is some way I can get a handle on the FPM instance inside my own class and control the button(s) from there.
Thanks in advance!