Use the beforeRenderResponse event to modify fields before they are rendered and displayed on the browser!
Thanks to the phase listener implementation in our framework I could also solve the following issue:
Modify fields (set value, set read only, set hide) before the page is displayed in the browser, ie. it should arrive “properly” displayed (what else 😉 )
Up until now I didn’t quite now when to call my Bean to do all the stuff above. Sometimes the fields were not available in the view hierarchy yet, sometimes it was too late and the page already rendered.
If you use it this way you can apply all those changes (even for new documents!):
Result:
The “read” only fields are only read only for employees of our company, as is the GEID (which is otherwise completely hidden)