Hiding an item conditionally through SPEL in OAF ( VO Extension + Personalization )
Posted
by Manoj Madhusoodanan
on Oracle Blogs
See other posts from Oracle Blogs
or by Manoj Madhusoodanan
Published on Sun, 17 Jun 2012 16:39:45 +0000
Indexed on
2012/06/17
21:20 UTC
Read the original article
Hit count: 579
/Apps
In this blog I will explain how to conditionally set property of an item through personalization.Let me discuss using a business scenario.
My customer wants to make Hold from Payment/ All Invoices column readonly when the Operating Unit is UK ( Configured in a lookup XXCUST_EXCLUDED_ORGS ).
Analysis
First thing is we have to find out the page and business components.
Page: /oracle/apps/pos/supplier/webui/QuickUpdatePG
View Object: oracle.apps.pos.supplier.server.SitesVO
Solution
Download oracle.apps.pos.supplier.server.SitesVO from $JAVA_TOP to JDEV_USER_HOME/myprojects.Make sure the transfer mode of the file (See below table).
File Type |
Transfer Mode |
.xml |
ASCII |
.class |
Binary |
.tar |
Binary |
.java |
ASCII |
Since there is no VO attribute available to determine the Site Org against the lookup Org we have to add the logic inside a custom VO attribute. So VO extension is required in this scenario.
Add an attribute "isPymtReadOnlyStr" in the existing query.This column returns 'Y' if there is a match in the lookup otherwise 'N'. Create a transient attribute "isPymtReadOnly" of type BOOLEAN.This will return TRUE if "isPymtReadOnlyStr" is "Y" otherwise FALSE.
The reason behind adding the "isPymtReadOnly" is we are setting the item property as readonly through SPEL.It will recognize only BOOLEAN.But SQL query doesn't support BOOLEAN.So we are building a BOOLEAN attribute from the SQL which will use in the personalization layer to set the item property.
Steps
1) Create a new VO xxcust.oracle.apps.pos.supplier.server.XXCUSTSitesVO which extends from oracle.apps.pos.supplier.server.SitesVO. Make sure the binding style should be same as SitesVO.
Create the XXCUSTSitesVO which same query of SitesVO.Later we will add the new attribute to XXCUSTSitesVO.
At this point of time all the existing VO attributes are of Updatable property as "Always".
Press Finish without creating XXCUSTSitesVORowImpl.java
2) Select the XXCUSTSitesVO from JDeveloper Application Navigator. Modify the query and add the extra column.
3) Create a new transient attribute as follows.
4) Once you modify the query all the existing attributes Updatable property will change to Never.So revert that property back to orginal.
5) Create XXCUSTSitesVORowImpl.java by checking the following check box.
6) Add the following code snippet in XXCUSTSitesVORowImpl.java
7) Create the substitution for SitesVO as follows.
Following entry will get created in current jpx file.
<Substitutes>
<Substitute OldName ="oracle.apps.pos.supplier.server.SitesVO" NewName ="xxcust.oracle.apps.pos.supplier.server.XXCUSTSitesVO" />
</Substitutes>
8) Migrate XXCUSTSitesVOImpl.java,XXCUSTSitesVORowImpl.java and XXCUSTSitesVO.xml from desktop to actual instance.
9) Migrate the substitution using jpximporter.
10) Restart the server and verify the substitution has done perfectly.
11) Go to /oracle/apps/pos/supplier/webui/QuickUpdatePG and personalize the page.Set the item read only property to ${oa.SitesVO.IsPymtReadOnly}
12) Click on Apply and in next page click on Return to Application.
Verify your output.
Note: You can remove the substitution using following script.Please click here.
© Oracle Blogs or respective owner