Using Expressions in a Multilingual Environment

In a multilingual environment, it is important for workflows to be language agnostic. As an example, if we have a workflow decision step checking for the Account Status being Active, but that workflow is in a French environment, the value will be Actif, so comparing to the literal value would incorrectly return false.

For this reason, expressions involving comparison to MLOV-enabled values should leverage the Language Independent Code (LIC), which would be the same across all languages. This can be done using the built-in LookupValue expression as shown in the following examples.

Decision Step Example

Assume a decision step compares Account Status to Active. The Account Status drop-down list bounds the Account Status field. You can set the Compare To property to Expression and set the Expression property to the following code:

 [Account Status] = LookupValue ("ACCOUNT_STATUS", "Active")

Business Service Step Example

To send an email to an expense approver, assume a business service step calls the Outbound Communications Manager. The Comm Recipient Group drop-down list bounds the Recipient Group argument. You can set the Type property to Expression and set the Value property to the following code:

LookupValue ("COMM_RECIP_SRC", "Comm Employee")

For more information about globalization, see Siebel Global Deployment Guide. For more information about defining Siebel Workflow to use MLOV capable fields, see Configuring Siebel Business Applications.