Customization can be enabled for each Planning application individually. There is an application property ORACLE_ADF_UI that can be set to true or false. It controls whether or not the application user interface appears using the Oracle Application Development Framework or as presented in version 188.8.131.52. The default in 184.108.40.206 is true.
The TotPlan demo application is being used for this post. This is how it appears in the ADF UI.
In the Application Properties tab click the add button to add the ORACLE_ADF_UI property, which isn’t listed by default.
This will add a new row for the property. In the Property Name column type in the ADF property. Then set it to false since we want the old 220.127.116.11 interface.
Click Save and you will get the following message. I’ve found that simply closing the application and then reopening it suffices to have the setting take effect. Your mileage may vary.
Step 2: Locate and open the ValidateData.js file
Here are the functions listed in the ValidateData.js file:
Step 3: Specify the application and forms to be customized
The first thing you’ll want to do is specify where you want customization to take place. Here is a snip of code that shows how to do this.
- applicationName – This is a variable that contains the currently opened form’s application’s name.
- formName – This is a variable that contains the currently opened form’s name.
- equalsIgnoreCase – This function has two string parameters. It compares the first string to the second string while ignoring capitalization and then returns a comparison between the two as follows:string1==string2. That’s why we can use it in an IF clause; if the returned comparison is true, whatever is specified in the IF clause is executed. If the returned comparison is false, the else clause contents is executed.
The code above executes as follows:
- First check if we’re in the TotPlan application, if not, the function ends.
- Then check if the “02 Product Revenue” is the opened form.
- If it is “02 Product Revenue”, an alert box opens notifying user that this is the opened form.
- If it isn’t, an alert box opens notifying user it’s a different form.
This is what we see when we open “03 Revenue Assump”.
And this is what we see when we open “02 Product Revenue”.
As you can see, it’s pretty simple to makes sure you’re working on only one specific application and/or form. In addition, you can use the double pipe OR operator to specify a list of forms as follows:
IF (equalsIgnoreCase(formName, “Form1?) || (equalsIgnoreCase(formName, “Form2?))
Step 4: Stay tuned for future posts
The “ORA-12154: TNS Oracle error message is very common for database administrators. Learn how to diagnose & resolve this common issue here today.
Most DBAs have struggled with the pros and cons of choosing one data type over another. This blog post discusses different situations.
If you’re confused about Oracle’s extended support deadlines, you are not alone. Here’s an overview of what’s in store for 11g through 19c.