Use Of Symbolic Strings Conversion Utility (consoleapp) During Siebel Upgrade (Doc ID 2049382.1)

Last updated on DECEMBER 10, 2015

Applies to:

Siebel CRM - Version 8.1.1 [21112] and later
Information in this document applies to any platform.

Goal

The Siebel Upgrade guide at:

Siebel Database Upgrade Guide > Siebel Postmerge Development Tasks > Upgrading to the Siebel Symbolic String Model

Mentions:
"The symbolic string model is object-oriented. As of Siebel CRM version 7.8.2, 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."

What would be the impacts of not running this utility against the merged repository and what would be the benefits of doing so?

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms