To create view objects for persons, right-click on the Model project and navigate to New | View Object. It's a good idea to give your view object a name that indicates its intended usage as a list of values. For the list of persons, use the name PersonLOV. Leave the data source at Entity Object.

In step 2 of the wizard, choose the Person entity object and move it to the box to the right. You can remove the checkmark in the Updatable box since we will only be using this view object for the drop-down list, as shown in the following screenshot:

In step 3 of the wizard, move the fields you want to the right-hand side—in this case, we just need Initials. Note that the primary key attribute will always be included, as shown in the following screenshot:

In step 5 (Query), you define the ordering of records by entering Initials in the Order By field. Then, click on Finish to create the view object.

Repeat this procedure to create the other two value list view objects, which are as follows:

To create a view object for tasks, look at the Task Overview, Edit page (UC008), and data model. You'll notice that we need fields for date and time, text, start where, flight number, end where, number of passengers, and service. All of this data comes from the XDM_TASKS table through the Task entity object.

Create a new view object (AllTasksVO), leaving the data source at Entity Object. In step 2 of the wizard, choose the Task entity object and move it to the right-hand side. As we will actually be updating data through the AllTasksVO view object, we leave the check mark in the Updatable checkbox.

In step 3, shuttle the following fields to the right-hand side:

Note that in the Available box on the left-hand side, all attributes are shown in alphabetical order, not in the order you placed them in the entity objects or the order they have in the database table.

Click on Next twice and choose to order by start_date. Then click on Next to get to Bind Variables (step 6).

Looking at the search box at the top of the screen sketch, you can see that we need to limit the tasks displayed by responsible person, programme, and text. Use the New button to create three bind variables called pResponsible, pProgramme, and pText (all of them of type String). You can leave the other settings in this step of the wizard at their default values.

When you're done, click on the Back button to return to step 5 of the wizard and add a WHERE clause that uses the bind variables. It should look similar to the following code:

 (:pResponsible is null or PERS_ID = :pResponsible)
and (:pProgramme is null or PROG_ID = :pProgramme)
and (:pText is null or upper(TEXT) like '%' || upper(:pText) || '%')

When you are done entering the WHERE clause, click on the Test and Explain button to verify that your SQL is valid. If you do not get the Query executed successfully message, fix your SQL.

In this case, we allow null values for the bind variables, so the SQL statement has to contain an OR branch handling this case. We are converting both the database TEXT column and the pText bind variable to upper case to achieve case-insensitive matching. We are also concatenating a wildcard character before and after the parameter value to search for occurrences of the search text anywhere in the database value.

When you click on Finish, the AllTasksVO view object is created and appears in the application navigator.

However, we are not quite done with the view object—we still need to define which data elements use lists of values. You might remember from the page layout illustration that Service was rendered as a drop-down listbox. Double-click on the AllTasksVO view object to edit it and choose the Attributes subtab on the left-hand side. Choose the ElemKey attribute and then select the List of Values tab at the bottom of the view object window. Click on the green plus sign to bring up the Create List of Values dialog, as shown in the following screenshot:

In this dialog, click on the green plus sign to add the List Data Source. Choose the ServiceLOV view object and then ElemKey as List Attribute.

Since we don't want to display the actual key value (ElemKey) to the user, choose the UI Hints tab and move the Description attribute to the right-hand side box. Uncheck the Include "No Selection" Item checkbox and then click on OK.

The Attributes tab also allows you to define some hints to the user interface components about rendering the component. Click on the StartDate attribute and choose the UI Hints tab at the bottom of the view object window. Set the label to Start time, set Format Type to Simple Date, and in the Format field, enter the format mask, dd-MMM-yy HH:mm.

Click on the remaining elements and set the label text, referring to the user interface sketch for UC008 (Format is only used for date and number objects).

To create an application module for tasks, right-click on the Model project and navigate to New | Application Module. Name the application module as EditTaskService. In step 2 of the wizard, expand the tree in the left-hand side and shuttle the AllTasksVO view object to the right, together with the PersonLOV and ProgrammeLOV that we need to create the search criteria value lists. This is all you need to do, so you can simply click on Finish to close the wizard.

Now, you can verify that your application module works the way you expected it to. In the Applications window, right-click on the EditTaskService application module node (the icon that looks like a little suitcase) and choose Run from the context menu. This will start the Oracle ADF Model Tester where you can work with all of the view objects that are part of your application module.

Double-click on the AllTasksVO1 view object instance. A pop-up dialog appears, allowing you to assign values to all the bind variables defined in the view objects. To begin, just click on OK to leave all bind variables at the NULL value. You should see the data in the AllTasksVO view object, as shown in the following screenshot:

Here, you can page through the existing data, as well as insert and delete rows, using the green plus and red cross symbols. Click on the Edit Bind Variables button (to the right of the toolbar, with the little pencil icon) to change bind variable values and notice how the data is filtered.

For the scheduling screen, we need two view objects: one for persons and one for the tasks assigned to persons.

We already have a view object showing persons, but this view object only contains the initials (because it was intended for the Persons drop-down list in UC008). We could create a new Persons view object for UC104; however, we'll change the existing view object instead.

First, you need to change the name of the view object from PersonLOV to PersonsVO to reflect that it's no longer just used for a list of values. Changing the name or package for existing objects is called refactoring, and JDeveloper makes this easy. Simply right-click on the PersonLOV view object and choose Refactor | Rename from the context menu. JDeveloper will change the name of the object and automatically update all of the references to it, as shown in the following screenshot:

Next, the view object needs some more attributes. To add these, open the view object by double-clicking on it and choose the Attributes subtab. Click on the little triangle next to the green plus sign above the attributes and choose Add Attribute from Entity, as shown in the following screenshot. Don't just click on the plus sign—you need to select the little triangle to get access to the Add Attribute from Entity menu item.

In the Attributes dialog, add the FirstName and LastName attributes to the Selected list and click on OK. Then, select the new FirstName attribute, select the UI Hints tab at the bottom of the view object window, and set a Label. Repeat this procedure for the LastName attribute.

Next, create another view object, giving it the name ScheduledTasksVO. In step 2 of the wizard, move the Task entity object to the right-hand side. As we won't be updating tasks either, you can remove the checkbox in the Updatable field here. In step 3 of the wizard, you only need to select the StartDate and EndDate attributes—note that the TaskId primary key attribute is automatically added.

In step 5 of the wizard, we need to add a WHERE clause so that the view object will only show tasks with both, a start and an end date. Enter the following WHERE clause:

start_date is not null and end_date is not null

Then, click on Finish.

Since there is a master-detail relationship between persons and tasks, we also need to create a view link. Right-click on the Model project and choose New | View Link. Name your view link PersonsTasksLink.

In step 2 of the wizard, we need to define the relationship between the two view objects. These are connected by the foreign key, XDM_PERS_TASK_FK, that defines the connection between a person and the tasks assigned to that person. Leave the Cardinality selection at 0..1 to * (this means that one person may have one or more tasks), expand the PersonsVO node on the left-hand side, and choose XdmPersTaskFkAssoc at the left-hand side of the link. On the right-hand side, expand the ScheduledTasksVO node and choose PersTaskFkAssoc again, this time at the right-hand side of the link. Then, click on Add. You can see the source and destination attributes added at the bottom of the dialog box, as shown in the following screenshot:

You don't need to change any of the remaining settings in this wizard, so you can simply click on Next and then Finish to close the dialog box.

Create another application module for the UC104 Person Task Timeline screen, giving it the name ScheduledTaskService.

In step 2 of the wizard, first move the PersonsVO view object to the right-hand side. Then, select the PersonsVO1 view object instance on the right-hand side and the node ScheduledTasksVO via PersonTasksLink on the left-hand side, and click on the > button to move ScheduledTasksVO to the right-hand side box, as shown in the following screenshot:

Note the difference between choosing ScheduledTasksVO on its own and choosing ScheduledTasksVO as a child of PersonsVO. If you choose the view object as a child of another view object, the ADF framework will automatically implement the master-detail relationship; the view object will only display the records that are children of the current record in the parent (master) view object. If you choose the view object on its own, it will not have any relationship to the master view object and will simply display all child records.

Then, click on Finish to close the wizard.

Run your new application module in the ADF Model Tester. In the left-hand side, you'll see the master view object, the view link, and the detail view object. Double-click on the view link to see the master and detail records together. When you use the navigation buttons at the master level, you will see different detail records displayed, as shown in the following screenshot: