Creating Power Forms using JD Edwards 9.0 Toolset
The following will discuss how to create a power form using the JD Edwards toolset. There is minimal coding involved to create the above form. This will walk you through the necessary steps to create the forms and link them so the Data Elements and Indexes forms automatically load based on the Primary Grid row selected.
Start OMW, click Add (in the project to be added to) and select Interactive Application. Start Designer.
Creating a Power Form – Tables and Fields Inquiry
Once in designer, click Form, Create, Power Browse. This will open the Power Browse Form Properties dialog box.
Adding a Business View to the Form.
Click the Edit button to the right of the Business View field.
Search for and select V9860A. Click OK.
Click the Entry Point checkbox in Settings. This will default this screen as the starting point for the application.
Insert fields into Grid
Make sure the Grid has focus, if not, click the Grid. In the Business View Column Browser, Highlight the field to add and double click the following fields : OBNM, MD, PFX
Change the names of the fields to match below.
To do this, right click on the field and select Properties (you can also double click the field to open the Properties dialog box). Click the Override Text checkbox and change the Column Headings. Click OK.
Add a filter field on the Form.
Click on the Form. Double click the field F9860.FUNO from the Business View Column Browser. Drop it on the form. Right click on the field and select Properties. Uncheck the Visible checkbox to hide the field. Next, click the Filter tab and click the = radio button. Click OK.
Right click on the Object Type text, select Properties, and uncheck the Visible attribute. Click OK. Click the Save () button.
Add an event rule in Post Dialog is Initialized.
Right click on the form, select Event Rules, Post Dialog is Initialized.
Click the button and set FC Object Type = TBLE. Click OK.
Creating a subform with a grid.
Select Insert from the main menu then select Subform.
Drop the subform on the primary form.
Next, add a grid to the new subform. Select Insert, Grid and drop grid on subform.
Associating a Business View to a Subform.
Right click on the subform and select Properties.
Click the Edit button to select a Business View. Search and select V98711A.
Click the OK button. Click the Save () button.
Defining a Data Structure to a Subform.
Reopen the subform Properties box (right click/Properties).
Click the edit button next to Data Structures. Since the key to the F98711 table is Object Name (OBNM), find that item in the Dictionary Items and drag it to the left.
Click OK. Click OK. You should now be back on the subform.
Adding a filter field to the Subform.
Now we will add the F98711.OBNM field on the subform so we can filter on it.
Double click the field F98711.OBNM from the Business View Column Browser. Drop it on the form.
Right click on the field and select Properties. Uncheck the Visible checkbox to hide the field.
Next, click the Filter tab and click the = radio button.
Click OK.
Right click on the text field and select Properties. Uncheck the Visible checkbox to hide the text field.
Click OK.
Click Save.
Inserting a find button on the subform.
From the main menu, click Insert, Push Button and drop it on the subform.
Double click the inserted button. On the General tab, deselect Visible.
On the Push Button tab, click the Find radio Button. Click OK.
Linking the Primary Form and the Subform.
First, review the data structure to be sure the proper values are available for the mapping link. You will need to link to key values of the subform. Right click on the primary form, select Properties and click the Edit button of the Data Structure. Change the data structure if necessary. Click OK.
Setting up the mapping link.
Click the Mapping Link tab. Select the appropriate field, click the right arrow and click OK. Click Save.
Functions necessary to find data on the subform.
On the Main grid, right click and select Event Rules.
Select Row is Selected (Web Only).
Click the System Function button () and open the Subform Functions folder.
Within that folder, select Notify Child.
Once opened, click on the Parameter Mapping tab.
Select FC Subform Title and click the right arrow () to move the form into the Value field. Click OK.
In order to have the subform find the data, we need to add the Trigger Default Child Action command.
To do this, click the System Function button and open the Subform Functions folder.
Within that folder, select Trigger Default Child Action. Map the Subform and Default Action (<Subform Find>).
Click OK. Click Save ().
Adding Business View fields to the subform.
Now we will add the Business View field OBND on the subform grid. Click on the subform grid so it has focus.
Insert F98711.OBND into Grid from the Business View Column Browser (highlight the field and double click). Click Save.
Next, right click on the subform, select Event Rules and select the Notified by Parent event rule.
Assign the proper Subform Interconnect variable to the FC Object Name field by click the button, selecting FC Object Name in the To Object column and selecting SI szNameObject in the From Object/Literal column. Click OK.
Save your Inquiry Application and test. It should look similar to the following.
Click on different rows and the records in the Subform should change.
Adding Data Dictionary fields to the subform.
Using the Alias column, add the following fields to the grid (drag and drop onto grid):
OWDI, DTAS, CDEC, OWER, OER1, OER2
Adding event rule logic to populate grid column fields.
Right click on the subform and select Event Rules.
Select Write Grid Line-Before.
Select the Table I/O button (). Select Fetch Single. Click Next.
Enter F9210 in the Object Name column and click Find. Click Next.
Map the matching grid column fields into the associated Alias rows.
Click Finish.
Click the save () button.
Save the application and test.
It should look similar to the following.
Disabling Page-at-a-Time Processing.
In order to have all rows returned for the grid, right click on the grid, select the Options tab and click the Disable Page-at-a-Time Processing in Grid checkbox. This is recommended for grids that will be returning a set amount of data.
Optional Additions:
1) Add another subform to the grid. Add a grid to the subform. We will use this to display the Primary and secondary keys for the selected table.
- Add business view V98713A to the subform.
- Add a data structure including the OBNM field.
- Add the following fields into the grid: INID, OBND, DESC, SRTO
- Add OBNM to the form and set the filter to =. Hide the field (uncheck Visible).
- Add a pushbutton on the form and make it a Find pushbutton. Hide the field.
- Set the sort order of the grid to be INID, SRTO. (Grid Properties)
- Disable Page-at-a-Time Processing.
- Add a mapping link from the parent form to the subform.
- Add event rule data on parent grid to notify child and find the data. (Since we would want the Find to run for all child subforms, you can either name each one or select All Children as the subform.)
- Add event rule logic on the subform to set the form control object name. (FC xxx = SI xxx)
- Rename the Subform Titles to be more meaningful. (Form Properties)
The finished form should look something like the following:
Page 1 of 11