Siebel Database Upgrade Guide > Siebel Postmerge Development Tasks >

Upgrading to the Siebel Symbolic String Model


Environments: Development environment only.

The symbolic string model is object-oriented. A single symbolic string replaces the text string translations. For each language, a text string is defined and assigned to the symbolic string as an attribute. This simplifies multilingual management of text strings throughout the UI.

Some strings will not be converted to the symbolic string model during upgrade. Seed data, error messages, lists of values (LOVs), and non-translatable attributes (such as the text alignment property on a control) will continue to use locale-based strings.

You must execute a conversion utility (consoleapp) to convert and consolidate your custom locale-based strings to the new model. If you plan to install a language pack, then it is recommended that you do so before you run the string conversion or consolidation process.

Instructions for converting or consolidating to the symbolic strings model are found in Using Siebel Tools.

Related Topics

About the Siebel Repository Merge

Upgrade Planning for Siebel String Translation

Siebel Database Upgrade Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.