There are some cases when we need to get a value associated to the new value that we have selected in a selectOneChoice, or that we have typed in an inputText.
In this cases we will not be able to get that value, as the only thing we can do is to get the new value from the ValueChangeListener object.
When developing ADF applications, a common way to create or update a record is doing it in a popup. There are many ways to do it that I have seen in some of my last ADF projects, for example:
In this post I am going to show you another way, using popupFetchListener.
In this example we are going to drag and drop Departments view object as a table (we don’t really need it but we can see the new created record), and 2 buttons, one for creating records and other for editing them.
In each button we are going to add a showPopupBehavior component with triggerType property set to action and popupId proerty set to the id of our popup.
Once we have the buttons, we create a popup and drag and drop departments view object as a form.
After that we have to create a popupFetchListener in the properties panel.
This will create a method in our bean where we have to check the button we have clicked in order the call CreateInsert opeartion only when we click on Create button.
The result of this implementation.
In one of our last projects we had the requirement to allow the user to filter tables using the table filter feature. By default you can filter String fields starting with the word that the user provides, but our customer needed to find the rows that contained the criteria.
This is an easy task that can be accomplished by creating a custom Query Listener method.
As by default the filter works with “Starts with” condition you will see that filtering by “tra” will give no result although departments like Administration exists.
In this example we will use Departments table in HR schema.
This is the helper method we use to call the default query listener.
The last step is to set our new method as the table’s query listener.
In one of our latest projects we had the requirement to create a reporting feature that based on some filters we had to built a custom query and display those results in a chart.
In this post I will show you the approach we followed.
The first step is to create a dummy view object. We are going to use SELECT * FROM DUAL as its query.
After this we need to add this view object to our Application Module data model and also create AM implementation class.
The main thing we are going to make is to create a List in our bean, based on a POJO that we will populate with our viewobject data.
We are going to add 3 attributes to our java class with their getter and setter methods.
After that, in our page’s bean we need to create a couple of properties. The first one is the List that will hold the values, and that will be the value property of the graph, and the second one is a String that will be the value property of the input where we will introduce the query.
The next method of the bean is the one to create the graph.
The first three lines let us create the viewobject a runtime passing the query and the view object instance.
In the rest lines of our method we are just iterating the view iterator and populating the graph List object.
The last step is to create the page that will looks like this
In the page definition file associated to the page we have to create the iterator binding that we are using in the bean.
While testing if we use this query, we will see a graph with the data.
This post is about the different ways that we have to display validation messages when, for example, an input component is marked as required or when other component such as af:validateDoubleRange is used to handle the validation.
We can have a simple form like this:
But if we have more than one validation error, the messages will be displayed in a popup.
We have a couple of properties to configure.
We can add this component, for example, in the top of the form and whenever we get a validation error al messages will be displayed in that area.
The second option is to add as many af:message as components we have so we can display validation errors inline next to the component that produces the error.
It doesn’t matter if we have 1 or more errors, all messages will be displayed inline, next to the component.
