OAF Personalization; Context, Security and Table

It has been a long time since i wrote here last time. The main reason is i was occupied with implementation of tough projects, but now i am back with some accumulated knowledge :)

In Forms context usage for descriptive flex fields (DFF) is easy; define the DFF Context Field Values and Forms automatically detects it.
Though for OAF screens additional setup is required; In the related OAF page> Personalize> Stil = Flex> Go> Personalize> Rendered=yes and
Segment list = Global Data Elements|SegmentName1|SegmentName2..||ContextCode1|SegmentName3..||ContextCode2|SegmentName4.. Then
related DFF' s column (Ex: iProcurement requisitions distributions DFF column: reqdistdffonacctcol) is set to Rendered = Yes

Personalization global link can be set for security reasons; "Personalize Self-Service Defn" profile can be set for making the link appear or disappear on OAF screens.

In OAF pages "FND: Personalization Region Link Enabled" profile provides the regional "Personalize" links to appear

To use standard OAF functionality "Disable Self-Service Personal" profile can be set

To set whether a user can or can not make OAF personalizations at site level: "FND: Personalization Seeding Mode" If you want to check the OAF personalization info and maybe even update it via the database following samples are handy: select * from jdr_paths where path_name like 'ShoppingHomePG' order by last_update_date desc edit jdr_attributes where ATT_COMP_DOCID in (80317,83558)