Guidelines for Using Code in an MLOV Configuration

If you use code in an MLOV configuration, then use the following guidelines:

• Do not hard-code the conditions for a dynamic drilldown or toggle applet. Instead, use the LookupValue function. A drilldown or toggle applet references a business component field that includes a value from a list of values. These values are dynamic. You must not hard-code them. For example, a dynamic drilldown might navigate the user in the following ways:

  • To a Credit Card screen if the account type is Credit Card

  • To a Savings screen if the account type is Savings

• Never use Siebel Visual Basic to hard-code the Display Value. Instead, use the language-independent code. Siebel Visual Basic does not include a function that gets a Display Value that is specific to a particular language. To write Siebel Visual Basic code using only language-independent code, you must create a calculated business component field that contains the language translation for a language-independent code.

• Use the LookupName function only in a calculated field or in a search specification. You cannot use it with Siebel scripting. For more information, see Options to Filter Data That Siebel CRM Displays in an Applet.

• For the Pre Default Value and Post Default Value properties of a business component field that uses a list of values list, always prepend the LookupValue function with Expr:. The first argument is the LOV Type. The second argument is the language-independent code. The function returns the Display Value for the language. For example:

  Expr: "LookupValue (""FS_PROD_ALLOC_RULES"", ""Default"")"
  

• If you define a search specification for a business component, link, applet, or list, then use the LookupValue function. For example:

  [Invoice Code] = LookupValue('FS_INVOICE_CODE', 'Auction')
  

  For more information, see Options to Filter Data That Siebel CRM Displays in an Applet.