1. Business Process Framework: Task UI Guide
  2. Guidelines for a Multilingual Task

Guidelines for a Multilingual Task

You can use values that are independent of any given language to design a task that Siebel CRM can run in multiple languages. Pay close attention to the following:

  • Display names that use symbolic strings. Do not use overrides.

  • Use LIC (language independent code) instead of a display value.

  • Values for the Task Property.

  • Field values for a business component and transient business component. For more information, see Overview of Transient Data.

  • Siebel operation steps.

  • Conditions.

  • LOVs.

  • Multilingual LOVs (MLOVs). If a LOV type is Multilingual, then Siebel CRM uses language independent code to store the data that the LOV binds.

  • Marked for translation.

About Literal Values in a Multilingual Environment

A literal value depends on a language, so a task cannot reference a literal value in a dynamic picklist and function correctly in a multilingual environment. A task that references a literal value is language dependent and you must not configure Siebel CRM to run it in a multilingual environment. A literal value in a dynamic picklist can include content that the user creates. These values reference content rather than metadata or an LOV, so they are variable and the task cannot reliably interpret them. For more information, see Siebel Global Deployment Guide.