Content Rules Get Corrupted with Many Extra Lines Added to Their "hda" Files
(Doc ID 820053.1)
Last updated on MAY 22, 2020
Applies to:Oracle WebCenter Content - Version 10.0 and later
Information in this document applies to any platform.
Oracle Universal Content Management - Version: 10.1.3.3.0 to 10.1.3.3.3
The following steps exhibit the behavior:
- The "affected" Rule(s) can be edited from Configuration Manager. Fields can be added to the rule(s) from the list of all fields
- After a new custom metadata field is added via Configuration Manager, the database updated, and you edit a "non affected" rule, the new metadata field is displayed in the list of available fields to be added to the rule
- Open an "affected" rule and the new metadata field is not displayed in the list and can not be added to the rule
- Reopen the "non-affected" rule and the new metadata field is no longer displayed in the list and can not be added to the rule
- Close and restart Configuration Manager
- Reopen the "non-affected" rule and the new metadata field is once again displayed in the list to be added to the rule
- Reopen the "affected" rule and the new metadata field still does not display
- Upon addition of other metadata fields to the "affected" rule, the new metadata field no longer displays for any "non-affected" rules, not until Configuration Manager is closed and started again.
The "affected" rule hda file(s) also contains these extra/incorrect sections:
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