FSTP: Default Values from Personalizations Not Actually Defaulting in e.g. HTML Debrief (OA Framework based) (Doc ID 1596256.1)

Last updated on SEPTEMBER 14, 2023

Applies to:

Goal

Using OA Framework personalizations it is possible to default values in fields. E.g. the value for the Item used in new labour debrief lines can be defaulted by setting a value in a personalization as follows:

1. Make sure that profile 'FND: Personalization Region Link Enabled' is set to Yes - if you have to make a change, bounce the middle tier web server before continuing
2. Go to the HTML debrief page
3. In the labor section, click on the Personalize "Labor Table"  link
4. Click Expand All
5. Find the 'Message Lov Input: Item' in this structure:
   Column: (column4) Yes
    Switcher: (LItemnumberswitcher) Yes
     Case_name_ L Item Number Disp
       Message Styled Text: (LItemNumberDisp) Yes
     Case_name_ L Item Number
       Message Lov Input: Item Yes
         Lov Mappings
           Lov Map: (lovMap1)
           Lov Map: (lovMap2)
           Lov Map: (lovMap3)
           Lov Map: (lovMap4)
   
6. Set the default value at 'Service Debrief Task' level to start with, by clicking on the edit icon for 'Message Lov Input: Item', entering a value for 'Initial Value'.
7. Apply.
8. When back in the main personalization screen, check the 'Include Personalized Items Only' checkbox and wait for the page to reload. It should then list only personalized items, including the one above
9. Now login again and retest the issue

What could cause the value for the personalized field to be empty even when this personalization is done and a new labour line is entered?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.