Let’s imagine the following scenario; or even better, let’s see the following picture:
We’ve got a home page with an embedded taskflow being shown as a region. When we select a node from the tree, we want to communicate to the Home Page that the selection has been made, passing also data in the form of a payload.
NoticiasD – A news reader ADF Application with custom skinning emulating what is now known as Linkedin Pulse. This POC Application was born with only one goal; show that ADF Applications can look as nice as any other web application you might have seen. Although the application itself is simple and far from being perfect, you may actually doubt that it was build using only adf components.
When creating and experimenting ADF Applications, a common thought or requirement would be to filter a table upon a selection from a LOV. This might sound straightforward to implement; Autosubmit to the LOV, ExecuteWithParams in the ValueChangeListener, partialTrigger on the table and buya, this should be enough. Later on you would find out that the behaviour is not the expected.
One of the great advantages of using ADF BC for your data model, is the possibility to use “Transient” attributes in them. A transient attribute means that it is not persistent in data base and it will filled manually or programatically to achieve a certain task within a requirement. For example, a requirement is to display the Average Employee Salary for a Department. If you think to