Forms Personalization
Forms Personalization is a standard feature provided by oracle and supported by oracle to customize the forms. With Forms personalization you can hide fiedls, make fields mandatory, create zoom functionality, change lov dynamically e.t.c
Related Articles:
WHEN-NEW-FORM-INSTANCE WHEN-NEW-BLOCK-INSTANCE WHEN-NEW-RECORD-INSTANCE WHEN-NEW-ITEM-INSTANCE WHEN-VALIDATE-RECORD MENUS SPECIAL EVENTS
No related Articles found...
A Form can have multiple functions. Having the personalization at function level limits the scope of the personalization. For example in Inventory for both “Master Item form” and “Organization Item form” uses same form named INVIDITM where as both have different fucntions linked to them.
No related Articles found...
Yes.
No related Articles found...
Yes. In the actions set DISPLAYED property to false.
No related Articles found...
No related Articles found...
Yes. Using global Variables.
No related Articles found...
Form Personlizations can be moved easily through FNDLOAD from one instance to other. Refer to the Article FNDLOAD for more details: http://www.erpschools.com/Apps/oracle-applications/articles/General/FNDLOAD-to-transfer-the-menus-concurrent-programs-personalization-from-one-instance-to-other/index.aspx
Related Articles:
Personalization gives us the ability to customize Forms in a very easy manner. The below customizations are possible through Personalization: Zoom from one form to another Pass data from one form to another through global variables Change LOV values dynamically Enable/Disable/Hide fields dynamically Display user friendly messages when required Launch URL directly from oracle form Execute PL/SQL programs through FORM_DDL package Call custom libraries dynamically
No related Articles found...
No related Articles found...
No related Articles found...
FORM level and FUNCTION level
No related Articles found...
The below can be done using PErsonalization: Zoom from one form to another Pass data from one form to another through global variables Change LOV values dynamically Enable/Disable/Hide fields dynamically Display user friendly messages when required Launch URL directly from oracle form Execute PL/SQL programs through FORM_DDL package Call custom libraries dynamically
Related Articles:
Refer to the Forms Personalization Tutorial article: http://www.erpschools.com/Apps/oracle-applications/articles/Tools/Forms/Personalization/Forms-Personalization-Tutorial/index.aspx
Related Articles:
Advantages: Personalizations are stored in tables rather than files Will not have a bigger impact when you upgrade or apply patches to the environment Can be moved easily through FNDLOAD from one instance to other Can be restricted at site/responsibility/user level Easy to disable/enable with click of a button. Personalization will store who columns with which we have the ability to track who created/modified it where as in CUSTOM.PLL we don¿t have that ability. Disadvantages: Not all can be customized using Personalization.
No related Articles found...
No. If it is normal message or warning data will be saved but not for error message.
No related Articles found...
admin
the above questions r very usefull to me.. thanks for u, can u give answers for below questions…
Can you use global variables in forms personalization? If so How?
How do you make a field mandatory or not mandatory using Forms Personalization?
Can you default a value in a text filed through personalization? How?
Can I get answer for this??
Can you default a value in a text filed through personalization? How?
Yes,
in the form personalization form, go to actions tab and thereselect object type as item, target object – ,
property value- “Initial Value”
value as the text that u want to default
How can you restrict the access (to oracle apps) to A GROUP OF users using personalization?
A. Node or Responsibility Trust Level : is profile option, to restrict access to set of responsibilities based on Web Server from which user logs in.
This profile option can take one of three values
Administrative
Normal (Default Value)
External
Can you default a value in a text filed through personalization? How?
A.
Responsibility: System Administrator
1 – Ensure to set system profile ‘Hide Diagnostics menu entry’ to ‘No’ and ‘Utilities:Diagnostics’ to ‘Yes’ at the user level.
2 – Open the Users form. (N) Security > User > Define.
3 – This is the basic Users form as shown here:
Oracle Basic Users Form
4 – From the menu, select (M) Help > Diagnostics > Custom Code > Personalize.
5 – If some Rules are already defined in the Users form, you will see them this window (as in this example).
6 – Add a new Rule by selecting (M) File > New.
7 – This is the Form Personalisation form and it’s Rules already defined. We will be adding seq. 40.
Oracle Form Personalization (Users)
A – Rules Seq.: 40
B – Description: Hide Person, Customer and Fax fields
C – Trigger Event: WHEN-NEW-FORM-INSTANCE
D – Context or Scope: Set at User level and enter your user in the Value field
E – Select the Actions tab. This is the Actions tab of Rule seq. 40
Oracle Form Personalization (Users) Actions tab
F – Action Seq.: 1
G – Type: Property
H – Object Type: Item
I – Select the Select By Text button
Oracle Form Personalization (Users) Actions tab Select by text button
J – Select the Person (Users) item from the LOV
K – Property Name: DISPLAYED
L – Value: False
M – Save your work
N – When you are done, it should look like this:
Oracle Form Personalization (Users) Actions tab Actions seq 1 final
O – Repeat Steps F to L for the Customer and Fax items. Save all of your work. It should now look like this:
Oracle Form Personalization (Users) Actions tab Actions all seq final
P – Close the Form Personalization form, close the User form and reopen it. Your User form should now look like this: Notice that the User, Customer and Fax fields are no longer displayed.
Oracle Form Personalization (Users) Final