Introduction To Form Personalization
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Introduction To Form Personalization as PDF for free.
More details
- Words: 1,900
- Pages: 31
Introduction to Form Personalization
1-1
Copyright © 2004, Oracle. All rights reserved.
Objectives After completing this module, you should be able to do the following: Invoke the Personalizations form Understand the basic structures : Rules, Context, and Actions Make simple changes like changing prompts and hiding objects Select objects by their current on-screen text Get the current value for properties Apply changes immediately to test their effect Disable personalizations 1-2
Copyright © 2004, Oracle. All rights reserved.
Related Course Material If you are not familiar with the basic construct of an Oracle Developer form, including terms such as block, record, item, trigger, property and builtin, you should consider a course such as Oracle Developer: Forms Fundamentals, offered by Oracle University. The viewlet Oracle Applications Form Personalization Demonstration shows many of the concepts included in this module.
1-3
Copyright © 2004, Oracle. All rights reserved.
Agenda
Overview of Form Personalization Rules and Conditions Context Actions Working with Strings Getting it right Putting it all Together Limitations Relationship to CUSTOM library Summary
1-4
Copyright © 2004, Oracle. All rights reserved.
All customers wish to: Remove fields, buttons, tabs, etc. from the screen because they never use them Re-label fields, buttons, tips to match their terminology Change the default value of fields Allow easy access from one form to another, passing context Do any of the above for only a particular user or responsibility Do any of the above only if certain conditions are true. Do all of the above without writing code, and without violating Support agreements
Your wish is granted! 1-5
Copyright © 2004, Oracle. All rights reserved.
Overview of Form Personalization • Allows you to make declarative changes to a form. • Changes get applied at runtime when the proper trigger event occurs. • Changes can get applied based on who you are and other conditions • You can: • Change object properties • Execute certain Forms builtins • Display messages • Activate menu entries 1-6
Copyright © 2004, Oracle. All rights reserved.
WARNING! Form Personalizations allows you to fundamentally alter the behavior of the product that Oracle ships, and access any and all data. Therefore, This feature should only be made available to trusted users. Avoid building Personalizations on a production system. – Form Personalizations should first be entered and thoroughly QA’ed on a test system before they are loaded to a production system 1-7
Copyright © 2004, Oracle. All rights reserved.
Invoking the Personalization screen Run the form that you want to modify Select Help > Diagnostics > CustomCode > Personalize from the pulldown menu –
Profiles ‘Utilities: Diagnostics’ and ‘Hide Diagnostics menu entry’ control access to this entry
The Personalizations screen will now run –
1-8
It will automatically query any rules if they exist for that function
Copyright © 2004, Oracle. All rights reserved.
Rules and Conditions
1-9
Copyright © 2004, Oracle. All rights reserved.
Rules and Conditions, continued Rules govern when personalizations get evaluated: Function Name: the name of the function that you ran. Personalizations are made for a function, not a form. Seq: an ordering from 1 (first) to 100 (last) Description: allows you to record why you are making the change Enabled: used to temporarily disable a rule Trigger Event: the event within the form that causes invocation of the rule Trigger object: the context for the trigger event, such as a particular block or item Condition: an optional SQL fragment that, when it evaluates to TRUE, allows the rule to execute. An Advanced class describes Conditions. 1-10
Copyright © 2004, Oracle. All rights reserved.
Context
1-11
Copyright © 2004, Oracle. All rights reserved.
Context , continued Context controls who personalizations apply to: Level: Site, Responsibility, Industry, or User Value: The specific value when level is Responsibility, Industry, or User At runtime, if the user’s context matches any context of a rule, that rule is executed.
1-12
Copyright © 2004, Oracle. All rights reserved.
Actions , continued Actions determine what the personalization does: Seq: an ordering from 1 (first) to 100 (last) Type: Property, Message, Builtin, or Special – Depending on the Type, the panel will change to show additional fields Description: allows you to record why you are making the change Language: a list of installed languages, and ‘ALL’ – An action associated with a specific language will only be executed in the context of that language Enabled: used to temporarily disable an action 1-13
Copyright © 2004, Oracle. All rights reserved.
Actions: Property
Used to set a property of an item
Select By Text…: choose an object by it’s onscreen text Object Type and Target Object: internal identifier of the object Property Name: the property to change Value: the new value Get Value: extract the current property value into the Value field 1-14
Copyright © 2004, Oracle. All rights reserved.
Actions: Property Example
This action:
Changes this screen:
1-15
To this:
Copyright © 2004, Oracle. All rights reserved.
Actions: Message
Used to display a popup message Message Type: Error, Warning, Hint, Question, Debug Message Text: the text of the message
1-16
Copyright © 2004, Oracle. All rights reserved.
Actions: Message Example This action:
Causes this dialog to appear:
1-17
Copyright © 2004, Oracle. All rights reserved.
Actions: Builtin
Used to perform processing by calling Forms and AOL functions Builtin Type: – – – – – –
GO_ITEM and GO_BLOCK DO_KEY RAISE FORM_TRIGGER_FAILURE, FORMS_DDL FND_UTILITIES.OPEN_URL FND_FUNCTION.EXECUTE
Arguments vary based on the Type 1-18
Copyright © 2004, Oracle. All rights reserved.
Actions: Builtin Example This action:
Opens the Responsibilities form (if the user has permission):
1-19
Copyright © 2004, Oracle. All rights reserved.
Actions: Special
Used to activate up to 45 pre-seeded menu entries
Menu Entry: SPECIAL1 through SPECIAL45 Menu Label: the text for the menu entry Render Line before menu: will draw a line above the menu entry Enabled In Block(s): the blocks for which the menu entry should be enabled. –
Leave blank for all blocks.
Icon Name: the name of a .ico file 1-20
Copyright © 2004, Oracle. All rights reserved.
Actions: Special Example
This action:
Activates the Tools menu and creates the menu entry, for all blocks of the form: 1-21
Copyright © 2004, Oracle. All rights reserved.
Working with Strings Every property that takes a string can work one of two ways If the string you type does not start with ‘=’, then it be used exactly as you typed it If the string you type starts with ‘=’, then it will be evaluated at runtime. You can refer to: – – –
1-22
bind variables, like :block.field SQL operators, such as ||, TO_CHAR(), DECODE(), and NVL() Server-side functions that do not have OUT parameters
Copyright © 2004, Oracle. All rights reserved.
Working with Strings Example This action:
Causes this dialog to appear (when run on 25-AUG-04):
1-23
Copyright © 2004, Oracle. All rights reserved.
Getting it right Various features and functions are available to assist you: Trigger and Target Objects are validated ‘Add
1-1
Copyright © 2004, Oracle. All rights reserved.
Objectives After completing this module, you should be able to do the following: Invoke the Personalizations form Understand the basic structures : Rules, Context, and Actions Make simple changes like changing prompts and hiding objects Select objects by their current on-screen text Get the current value for properties Apply changes immediately to test their effect Disable personalizations 1-2
Copyright © 2004, Oracle. All rights reserved.
Related Course Material If you are not familiar with the basic construct of an Oracle Developer form, including terms such as block, record, item, trigger, property and builtin, you should consider a course such as Oracle Developer: Forms Fundamentals, offered by Oracle University. The viewlet Oracle Applications Form Personalization Demonstration shows many of the concepts included in this module.
1-3
Copyright © 2004, Oracle. All rights reserved.
Agenda
Overview of Form Personalization Rules and Conditions Context Actions Working with Strings Getting it right Putting it all Together Limitations Relationship to CUSTOM library Summary
1-4
Copyright © 2004, Oracle. All rights reserved.
All customers wish to: Remove fields, buttons, tabs, etc. from the screen because they never use them Re-label fields, buttons, tips to match their terminology Change the default value of fields Allow easy access from one form to another, passing context Do any of the above for only a particular user or responsibility Do any of the above only if certain conditions are true. Do all of the above without writing code, and without violating Support agreements
Your wish is granted! 1-5
Copyright © 2004, Oracle. All rights reserved.
Overview of Form Personalization • Allows you to make declarative changes to a form. • Changes get applied at runtime when the proper trigger event occurs. • Changes can get applied based on who you are and other conditions • You can: • Change object properties • Execute certain Forms builtins • Display messages • Activate menu entries 1-6
Copyright © 2004, Oracle. All rights reserved.
WARNING! Form Personalizations allows you to fundamentally alter the behavior of the product that Oracle ships, and access any and all data. Therefore, This feature should only be made available to trusted users. Avoid building Personalizations on a production system. – Form Personalizations should first be entered and thoroughly QA’ed on a test system before they are loaded to a production system 1-7
Copyright © 2004, Oracle. All rights reserved.
Invoking the Personalization screen Run the form that you want to modify Select Help > Diagnostics > CustomCode > Personalize from the pulldown menu –
Profiles ‘Utilities: Diagnostics’ and ‘Hide Diagnostics menu entry’ control access to this entry
The Personalizations screen will now run –
1-8
It will automatically query any rules if they exist for that function
Copyright © 2004, Oracle. All rights reserved.
Rules and Conditions
1-9
Copyright © 2004, Oracle. All rights reserved.
Rules and Conditions, continued Rules govern when personalizations get evaluated: Function Name: the name of the function that you ran. Personalizations are made for a function, not a form. Seq: an ordering from 1 (first) to 100 (last) Description: allows you to record why you are making the change Enabled: used to temporarily disable a rule Trigger Event: the event within the form that causes invocation of the rule Trigger object: the context for the trigger event, such as a particular block or item Condition: an optional SQL fragment that, when it evaluates to TRUE, allows the rule to execute. An Advanced class describes Conditions. 1-10
Copyright © 2004, Oracle. All rights reserved.
Context
1-11
Copyright © 2004, Oracle. All rights reserved.
Context , continued Context controls who personalizations apply to: Level: Site, Responsibility, Industry, or User Value: The specific value when level is Responsibility, Industry, or User At runtime, if the user’s context matches any context of a rule, that rule is executed.
1-12
Copyright © 2004, Oracle. All rights reserved.
Actions , continued Actions determine what the personalization does: Seq: an ordering from 1 (first) to 100 (last) Type: Property, Message, Builtin, or Special – Depending on the Type, the panel will change to show additional fields Description: allows you to record why you are making the change Language: a list of installed languages, and ‘ALL’ – An action associated with a specific language will only be executed in the context of that language Enabled: used to temporarily disable an action 1-13
Copyright © 2004, Oracle. All rights reserved.
Actions: Property
Used to set a property of an item
Select By Text…: choose an object by it’s onscreen text Object Type and Target Object: internal identifier of the object Property Name: the property to change Value: the new value Get Value: extract the current property value into the Value field 1-14
Copyright © 2004, Oracle. All rights reserved.
Actions: Property Example
This action:
Changes this screen:
1-15
To this:
Copyright © 2004, Oracle. All rights reserved.
Actions: Message
Used to display a popup message Message Type: Error, Warning, Hint, Question, Debug Message Text: the text of the message
1-16
Copyright © 2004, Oracle. All rights reserved.
Actions: Message Example This action:
Causes this dialog to appear:
1-17
Copyright © 2004, Oracle. All rights reserved.
Actions: Builtin
Used to perform processing by calling Forms and AOL functions Builtin Type: – – – – – –
GO_ITEM and GO_BLOCK DO_KEY RAISE FORM_TRIGGER_FAILURE, FORMS_DDL FND_UTILITIES.OPEN_URL FND_FUNCTION.EXECUTE
Arguments vary based on the Type 1-18
Copyright © 2004, Oracle. All rights reserved.
Actions: Builtin Example This action:
Opens the Responsibilities form (if the user has permission):
1-19
Copyright © 2004, Oracle. All rights reserved.
Actions: Special
Used to activate up to 45 pre-seeded menu entries
Menu Entry: SPECIAL1 through SPECIAL45 Menu Label: the text for the menu entry Render Line before menu: will draw a line above the menu entry Enabled In Block(s): the blocks for which the menu entry should be enabled. –
Leave blank for all blocks.
Icon Name: the name of a .ico file 1-20
Copyright © 2004, Oracle. All rights reserved.
Actions: Special Example
This action:
Activates the Tools menu and creates the menu entry, for all blocks of the form: 1-21
Copyright © 2004, Oracle. All rights reserved.
Working with Strings Every property that takes a string can work one of two ways If the string you type does not start with ‘=’, then it be used exactly as you typed it If the string you type starts with ‘=’, then it will be evaluated at runtime. You can refer to: – – –
1-22
bind variables, like :block.field SQL operators, such as ||, TO_CHAR(), DECODE(), and NVL() Server-side functions that do not have OUT parameters
Copyright © 2004, Oracle. All rights reserved.
Working with Strings Example This action:
Causes this dialog to appear (when run on 25-AUG-04):
1-23
Copyright © 2004, Oracle. All rights reserved.
Getting it right Various features and functions are available to assist you: Trigger and Target Objects are validated ‘Add
Related Documents
Introduction To Form Personalization
May 2020 15
Intermediate Level Form Personalization
May 2020 3
Form Personalization By A.passi
May 2020 11
Administrator Level Form Personalization
May 2020 9
Advanced Level Form Personalization
May 2020 10
Resctict Lov Form Personalization
May 2020 10More Documents from "Saurabh Sonkusare"
Introduction To Form Personalization
May 2020 15
Intermediate Level Form Personalization
May 2020 3
Administrator Level Form Personalization
May 2020 9
Oa-framework-tutorial-1233734243009882-2
May 2020 4
Advanced Level Form Personalization
May 2020 10