How to Convert Existing DCL to Schema in Content Server 7x
(Doc ID 445360.1)
Last updated on JANUARY 27, 2017
Applies to:Oracle Universal Content Management - Version: 7.0.0 to 7.5.1
Information in this document applies to any platform.
We have the DCL (Dependent Choice List) component enabled on SCS version 6 and would like to upgrade to SCS version 7. The DCL component of version 6 has been replaced with Schema in Content Server 7. How can we convert the current DCL format to Schema?
Disclaimer: This is not a core configuration. This is a custom feature extension of the software and is therefore only supported via the purchase of Consulting Services effort. With all customizations, when you upgrade your software, the custom changes may be overwritten. For more information on Customizations see: <
The DCL component for Stellent Content Server 6 allowed people to create DCLÃ¢ÂÂs through a web based user interface. The typical DCL Component has three associated custom metadata fields: IndChoice, DepChoice, and SubDepChoice with a dChoiceLevel value of 0, 1, and 2 respectively. Along with the user interface, a choice list was kept and maintained by an administrator.
Schema, introduced in Content server 7, provided the ability to create DCLÃ¢ÂÂs using data from pre-existing database tables. Relationships between this data could then be defined and leveraged to populate custom metadata fields.
This article outlines the steps necessary to leverage SCS version 6 DCLÃ¢ÂÂs and make them functional in SCS version 7.
NOTE: If the creation of a brand new schema based DCL is the goal, do not attempt to use these conversion guidelines, instead use Schema to implement a new design.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!