This entry is based on previous entries from John and Shray that deal with the same topic and provide the same type of solution. John’s entry was created before VBCS provided the UI id for components, and Shray’s entry is dealing with a more complex scenario that also involve fetching new data. So I figured I’ll write my version here – mostly for my own future reference if I’ll need to do this again.
The Goal is to show how you can modify the UI shown in a VBCS page in response to data changes in fields. For example how to hide or show a field based on the value of another field.
To do this, you need to hook into the HTML lifecycle of your VBCS page and subscribe to events in the UI. Then you code the changes you want to happen. Your gateway into manipulating/extending the HTML lifecycle in VBCS is the custom component available in the VBCS component palette. It provides a way to add your own HTML+JavaScript into an existing page.
The video below shows you the process (along with a couple of small mistakes along the route): Read the complete article here
Developer Partner Community
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.
Blog Twitter LinkedIn Forum Wiki
Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic, WebLogic Community,Oracle,OPN,Jürgen Kress
