Skip to main content

JHeadstart 11g TP - Magic with Wizards

One of the main features in ADF 11g is the use of taskflows. There are different kinds of taskflows. One of these is a process train. A process train (the ADF name for wizard) can be used to guide the end user step by step through a rather difficult process. In this post I describe how you can use JHeadstart to generate the wizard for you.

The very difficult (duh) process in his case is the entry of a new employee. For that I need a three step wizard.

The first steps are the same as always. Create a new fusion wep application, create new Business Components from tables, and only pick the Departments and Employees, enable JHeadstart on the view controller project, and finally create a new service definition for the datacontrol (accept al the defaults).

According to JHeadstart help, to spread items of one group over multiple wizard pages, you should place the items in an item region and set the layout style of the regions container to "separatePages". Let's do that.

Create three item Regions under the Employees group. The first one will contain "Personal" items, the second one the "Financial" data, and the last one contains all the other data. Set the layout style for the regions container to "separate pages". Take a look at the image below for the details.
Drag all the items from the Employees group to the appropriate item groups.

Now prepare the employees group to be generated as a wizard. First of all set the layout style to form, and check the "Wizard Style Layout" checkbox. Searching in a wizard is a little bit strange so set both Advanced- and Quick search properties to "none". In the operations part uncheck the "Single Row Update- and Delete" boxes and set "Display New Row on Entry" to true. The application Definition of the wizard should look something like this:


Finally generate the application and run it.
Notice how you can step through the wizard using the buttons and the train stations.


Fill out the fields in all three steps of the wizard and click finish.

If the entered data is correct JHeadstart will show the transaction completed message.


This was a very simple wizard. More complex magic can be done with wizards, but for now this will do.

Comments

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 …