PAXPREPR: Projects Form Personalization In The Trigger PROJECT_FOLDER.SEGMENT1_MIR.WHEN-NEW-ITEM-INSTANCE Is Not Working After Upgraded From R12.1.3 To R12.2.11
(Doc ID 2927956.1)
Last updated on AUGUST 09, 2024
Applies to:
Oracle Project Foundation - Version 12.2.11 and laterInformation in this document applies to any platform.
Symptoms
After upgraded from R12.1.3 to R12.2.11, Projects form personalization in the trigger PROJECT_FOLDER.SEGMENT1_MIR.WHEN-NEW-ITEM-INSTANCE is not working.
Patch 34714851:R12.PJF.C has been applied, but the issue still remains.
The same personalization is working correctly on R12.1.3.
Steps to Reproduce
==============
1. Login a Projects responsibility
Navigate: Projects
2. In the Projects form
Do: Help >> Diagnostics >> Custom Code >> Personalize
Function Name = PA_PAXPREPR_PROJECT
Condition:
Trigger Event = WHEN-NEW-ITEM-INSTANCE
Trigger Object = PROJECT_FOLDER.SEGMENT1_MIR
Condition = :PROJECT_FOLDER.PROJECT_TYPE NOT IN ('<project_type1>','<project_type2>','<project_type3>')
Actions:
Type = Property
Object Type = Block
Target Object = PROJECT_FOLDER
Property Name = UPDATE_ALLOWED
Value = FALSE
Type = Property
Object Type = Block
Target Object = PROJECT_FOLDER
Property Name = INSERT_ALLOWED
Value = FALSE
Type = Property
Object Type = Block
Target Object = PROJECT_FOLDER
Property Name = DELETE_ALLOWED
Value = FALSE
-Save
-Validate and Apply
3. Testing the form personalization:
a. In the Projects form
b. Search an existing project that has project type = <project type_4>
c. Open the project
Based on the personalization setup in step #2, this field should be grayed out (not updateable) because the project has project type of <project type_4>
which is not in <project_type1> or <project_type2> or <project_type3>.
Changes
Upgraded from R12.1.3 to R12.2.11
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |