Skip to main content

JHeadstart 11g TP - Master Detail and Overflow

I have been working with JHeadstart 11g technical preview a lot lately. I want to share some of the features with you in a series of articles. Luckily Oracle allowed me to blog about the JHeadstart 11g technical preview. It is a technical preview, but is already pretty mature. Let's start with some basic generation. In this blog I describe how easy it is to create a layout in which a master-detail relation is generated into a form - table layout. I use the DEPT-EMP relation we probably all know.

In the model project just create new Business Components from tables, and only pick the Departments and Employees. In the JHeadstart Application Definition Editor, you can now create a new Group, based on the Departments collection. Also create a detail Group based on the Employees group. It should look somewhat like this.

Before you generate, make sure that the layout style for the departments group is form. Also set layout style for employees to table, put this group on the same page, and below its parent. That sounds like a lot of laying out, but you can set all of this in the Group Layout properties of the Employees group.

Now run the generator, start the application and be amazed.........

And to make it all better, the simple and advanced search for the departments is generated for you as well.

Let's take this one step further. The Employees table contains a little bit too much columns. We will put these in a synchronized overflow area. Create two new item regions within the employees group. Call one "contact" and call the other one "financial".

For all items (except First name, Last name and Hiredate) in the Employees group set display in form and table to false. Now you can pick some items from the Employees group and drag them into these new regions. Now there is just one change to make before we can generate our new layout. On the Employees group you'll have to set the "Table overflow style". For now just pick "below with splitter".

Generate the application and run it.

Play around with the splitter to get all data in view, or even click on the splitter to hide the whole table. Pretty cool isn't it ! And how much code was involved ?

Actually this is not my prefered layout. It would be better to display these very few items to the right of the table. To achieve this put both item regions in a region container. By doing that we can use an accordion layout. This will enable the user to show/hide the details. Just create a new region container, set its layout style to accordion. Call the region "Details" or any other name you like, and drag the two groups we created earlier, into this new group. Change the layout style of the Employees group, by setting its "table overflow style" to "Right".

This should do the trick. Regenerate and run. Notice how the details are now displayed to the right of the table.

So in just very little time we created a master-detail page with an overflow area rendered in an accordion. All of the data is kept in sync with each other, and we have a cool layout.

For today that's all. Next time more on generating ADF applications with JHeadstart 11g.


Popular posts from this blog

ADF 12.1.3 : Implementing Default Table Filter Values

In one of my projects I ran into a requirement where the end user needs to be presented with default values in the table filters. This sounds like it is a common requirement, which is easy to implement. However it proved to be not so common, as it is not in the documentation nor are there any Blogpost to be found that talk about this feature. In this blogpost I describe how to implement this.

The Use Case Explained
Users of the application would typically enter today's date in a table filter in order to get all data that is valid for today. They do this each and every time. In order to facilitate them I want to have the table filter pre-filled with today's date (at the moment of writing July 31st 2015).

So whenever the page is displayed, it should display 'today' in the table filter and execute the query accordingly. The problem is to get the value in the filter without the user typing it. Lets first take a look at how the ADF Search and Filters are implemented by the f…

ADF 11g Quicky 3 : Adding Error, Info and Warning messages

How can we add a message programatically ? Last week I got this question for the second time in a months time. I decided to write a short blogpost on how this works.

Adding messages is very easy, you just need to know how it works.
You can add a message to your faces context by creating a new FacesMessage. Set the severity (ERROR, WARNING, INFO or FATAL ), set the message text, and if nessecary a message detail. The fragment below shows the code for an ERROR message.

1: public void setMessagesErr(ActionEvent actionEvent) {
2: String msg = "This is a message";
3: AdfFacesContext adfFacesContext = null;
4: adfFacesContext = AdfFacesContext.getCurrentInstance();
5: FacesContext ctx = FacesContext.getCurrentInstance();
6: FacesMessage fm =
7: new FacesMessage(FacesMessage.SEVERITY_ERROR, msg, "");
8: ctx.addMessage(null, fm);
9: }

I created a simple page with a couple of buttons to show the result of setting the message. When the butto…

How to: Adding Speech to Oracle Digital Assistant; Talk to me Goose

At Oracle Code One in October, and also on DOAG in Nurnberg Germany in November I presented on how to go beyond your regular chatbot. This presentation contained a part on exposing your Oracle Digital Assistant over Alexa and also a part on face recognition. I finally found the time to blog about it. In this blogpost I will share details of the Alexa implementation in this solution.
Typically there are 3 area's of interest which I will explain. Webhook Code to enable communication between Alexa and Oracle Digital AssistantAlexaDigital Assistant (DA) Explaining the Webhook Code The overall setup contains of Alexa, a NodeJS webhook and an Oracle Digital Assistant.
The webhook code will be responsible for receiving and transforming the JSON payload from the Alexa request. The transformed will be sent to a webhook configured on Oracle DA. The DA will send its response back to the webhook, which will transform into a format that can be used by an Alexa device. To code exposes two REST …