Symbolic Strings Conversion Utility during Siebel Upgrade as part of Post Merge Activities
Hi,
We have just finished with our Repository Merge and the Post Merge utilities as part of the upgrade from 7.8.2.14 to 8.1.1.7. Since we started our application from 7.8.2.14 and it is a single language ENU application, so should we run the Symbolic String Conversion utility? I do not see a need to run this utility as the symbolic string model was introduced in 7.7 but there some text in the Upgrade Guide that confuses me-
"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 localebased strings to the new model."
We have just finished with our Repository Merge and the Post Merge utilities as part of the upgrade from 7.8.2.14 to 8.1.1.7. Since we started our application from 7.8.2.14 and it is a single language ENU application, so should we run the Symbolic String Conversion utility? I do not see a need to run this utility as the symbolic string model was introduced in 7.7 but there some text in the Upgrade Guide that confuses me-
"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 localebased strings to the new model."
0