Best Practice for dynamiclly hiding/displaying fields on View
We are searching for some best practice /guideline to hide certain fields on a view at certain conditions.
F.e.: On View BP_HEAD/AccountDetails the field BP_GROUP should only be visible if an account (customer) has not been saved yet.
In any other case the field should not be visible. Please keep in mind BP_HEAD/AccountDetails is reused at other places.
My first attempt was to override in Contextnode 'HEADER' the attributes BP_GROUP GET_A_BP_GROUP method and controll the field`s visibility via return value rs_sfw_data‐reaction. But this attempt will render empty htmltablecells i.e. the webform shows whitespaces instead of labels/controls, which is pretty ugly in my opinion.
Hiding & displaying fields should be a common requirement, so is there any best practice approach leading to a webform without whitespaces but also providing the flexibility of GETTERs?
We also thought about using several View configurations, but as the views are used at several places (in this case f.e. also to edit an existing Account) and different fields might be required to be shown/hidden in different scenarios, this doesn`t seem to be an appropriate solution, as it would probably lead to a bunch of view configs.
Thanks for any feedback!