Utilizing Custom Profile_Trigger for Profiles in WebCenter Content (WCC) causes Issues with Profiles (i.e. following Migration)
(Doc ID 2316693.1)
Last updated on APRIL 10, 2024
Applies to:
Oracle WebCenter Content - Version 11.1.1.2.0 and laterInformation in this document applies to any platform.
Symptoms
Following migration from one WCC system to another an issue was presented when a customer Profile_Trigger field was being utilized.
Issue Example:
Profile selected for a Framework Folder is not the set profile trigger expected when attempting to add content in the folder. The metadata values are not the values or form associated with the selected profile.
STEPS TO REPRODUCE
-----------------------
The above issue can be reproduced at will with the following steps:
1. Log into WebCenter Content (WCC).
2. Navigate to a Framework Folder.
3. Click "Edit" and select "Metadata Values".
4. Switch PROFILE.
5. Click "Save".
6. Navigate to Add > New Content item.
7. Profile (from step 4) not selected (metadata values not updated)
Forced to re-select profile where it should have defaulted to the selected profile.
Changes
Custom Profile_Trigger is changed to default Profile_Trigger in Configuration Manager.
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 |