Implementation parameter pop-up window in ebs oaf Development

Implementation parameter pop-up window in ebs oaf Development

(Copyright statement: If your original or translated articles need to be reprinted, or if they are used for personal learning, please indicate the source; otherwise, please contact me. violators must investigate)

Overview

The parameter pop-up window is different from the embedded pop-up window. It has an independent area and is not embedded in the use page. The content in it is obtained and generated as needed, it has its own AM and page status, and handles popup page events differently. Both pop-up windows are only supported by the following four components, and cannot be changed or moved.

1. Text (messageStyledText)

2. Image

3. Link

4. Button

Step for implementing the parameter pop-up window

1. Create an independent RN, which will be used as a parameter pop-up window, which contains the controls you need.

2. On the Jdev structure panel, on the page where you want to display the parameter pop-up window, select the control area that contains the control to display the pop-up window.

3. Create a new region and set its type to popUp.

4. set Reasonable attribute values for the above popUp area, such as ID, Title, Region (RN in step 1), Type (embedded or parametric), Width, Height, Parameters, modal Enabled (whether it is a Modal window, if yes, the user cannot deal with the basic page ).

5. on the Jdev structure panel, select the control (only messageStyledText, image, link, or button can be displayed) and set the following attributes PopupId (the ID of the Popup control ), popupRenderEvent (what event pop-up window, such as onClick or onHover, the default value is onClick), PopupEnabled (whether to enable popup, the default value is false), ReadOnly (whether the pop-up window is read-only, if yes, when the mouse is not displayed, the window is closed. The default value is false ).

Implementation example

1. Create the RN of the parametric pop-up window, as shown below, specifying AM, and the vo attributes bound to each control. The creation process of AM, VO, and CO is the same as that of common ones, and is omitted.

2. Create the PG, AM, VO, CO, and so on pages to be used.

3. you can add a flowLayout or other container to the table in the Table above the basic page, because the popup cannot be directly put into the table, and then add the popup control to it, set the Parameters as follows. Note the Parameters attribute because the parameter pop-up window has its own AM, which is the main way to interact with the basic page, in addition, it cannot use EL (Expression Language, called SPEL (SimplestPossible Expression Language before 12.2). For more information, see <ebs oaf 12.2 development support for EL (ExpressionLanguage)>, http://blog.csdn.net/tavor/article/details/19645421), but to use the tag (TOKEN) that I introduced in <EBS OAF URL in development, encryption and encoding>, http://blog.csdn.net/tavor/article/details/23971889

4. Add a link control under the table. Its attribute settings are as follows. The Popup Id specified in the control is the Popup ID in step 3 above.

5. Add the following method to the AM of popup for ID initialization. Here the simplest logic is written.

6. Add the following to Popup CO to call the AM method based on the parameters passed in on the basic page to initialize VO.

7. The running result is as follows. Click the link and the corresponding manager information is displayed.