ADF drag and drop data binding allows you to bind UI components on a page to data or actions. You will use both techniques: you will create a form to edit orders data, and you will bind a button to the commit action.
The role of the edit page is to allow the user to add and modify data. You will add databound components to the
ed-o.jspx page to create an editable input form. The edit page is accessed from the browse page; at runtime when users click the Edit button on the orders form of the browse page, the application navigates to the edit page where the complete details of the order that is currently displayed on the orders form are available for editing. For saving changes to the database, you will add a Commit button to the edit page.
To begin designing the edit page, use the Data Controls panel again. To create the editable input form for an order, you will drag and drop OrdersView1, the same data collection you used to create the read-only form on the browse page. After creating the input form, you will use the Operations | Commit node under the expanded FODModuleDataControl node to add a Commit button.
In a previous cue card when you created the page flow diagram, you defined the navigation outcome
goBrowse from the edit page to the browse page. On the edit page, to provide access back to the browse page, you will add a command button and set the button's
action property to the
goBrowse outcome. At runtime when users execute the command button, the application navigates to the browse page.
Copyright © 1997, 2009, Oracle. All rights reserved.