Oracle Forms Personalization
Oracle has introduced a mechanism which revolutionizes the way the forms can be customized to fulfill the customer needs.Oracle Applications has provided a custom library using which the look and behavior of the standard forms can be altered, but the custom library modifications require extensive work on SQL and PL/SQL.Oracle Applications release 11.5.10 has provided a user interface “Personalization form” which will be used to define the personalization rules.
By default the “Personalize” menu is visible to all the users; this can be controlled with help of
profile options.By setting up the below profile options,access to the Personalize menu can
be limited for the authorized users.
Utilities: Diagnostics = Yes/No
Hide Diagnostics = Yes/No
invoking the Personalization form click on “Help -> Diagnostics -> Custom Code -> Personalize”
The form mainly contains four sections.
• Rules
• Conditions
• Context
• Actions
Rules:
Each rule contains a sequence number and the description. The rule can be activated or de-activated using the “Enabled” checkbox.
Oracle has introduced a mechanism which revolutionizes the way the forms can be customized to fulfill the customer needs.Oracle Applications has provided a custom library using which the look and behavior of the standard forms can be altered, but the custom library modifications require extensive work on SQL and PL/SQL.Oracle Applications release 11.5.10 has provided a user interface “Personalization form” which will be used to define the personalization rules.
By default the “Personalize” menu is visible to all the users; this can be controlled with help of
profile options.By setting up the below profile options,access to the Personalize menu can
be limited for the authorized users.
Utilities: Diagnostics = Yes/No
Hide Diagnostics = Yes/No
invoking the Personalization form click on “Help -> Diagnostics -> Custom Code -> Personalize”
The form mainly contains four sections.
• Rules
• Conditions
• Context
• Actions
Rules:
Each rule contains a sequence number and the description. The rule can be activated or de-activated using the “Enabled” checkbox.
Conditions
Conditions decide the event the rule to be executed. Each condition mainly contains three
sections i.e. Trigger Event, Trigger Object and Condition..
Context
Context manages to whom the personalization should apply. This is similar to the concept of
using profile options in Oracle Application
Context manages to whom the personalization should apply. This is similar to the concept of
using profile options in Oracle Application
Actions
Actions decide the exact operation to be performed when the conditions and context return true
during the runtime.
Actions decide the exact operation to be performed when the conditions and context return true
during the runtime.
Change the “Order Type” label to “Claim Type”
1.Open the Sales Order Form
2.Open the Personalization form using the navigation “Help Diagnostics Custom Code Personalize”
3.Enter the sequence number as 10 and description as “Change the Order Type Prompt to
Claim Type”
4.Select the Trigger Event as “WHEN-NEW-FORM-INSTANCE”
5.Select or enter the following values under Context section
• Level = Responsibility
• Value = Order Management Super User
On Actions tab, enter or select the following values
• Sequence = 10
• Type = Property
• Description = Order Type to Claim Type
• Language = All
• Enabled = Yes
Click on “Apply Now” button
Close both the forms and reopen the Sales Order form
The Order Number label should reflect as Claim Number
No comments:
Post a Comment