Siebel eService Administration Guide Addendum for Industry Applications > Siebel eService for Communications, Media, and Energy > Differences Between Siebel eService and Siebel eService for CME >

Differences in Personalization for CME

Personalization changes exist for customer applications because a single contact can have multiple accounts in Siebel eService Communications, Media, and Energy.

Any account-specific personalization rules are evaluated using the primary account of the contact. When the contact logs in, the login process loads the profile for contact's primary account into memory. When the contact selects an account, the process does not flush the profile of the primary account out of memory and load a new one. Table 18 shows the profile attribute values that the process changes.

You cannot change this behavior, so account-driven personalization rules always use the primary account of the contact.

However, if you want to use a specific field value of the current account for personalization, then you can write Siebel VB (Visual Basic) code to get the field value from the account. When the user selects an account, the following global variables that can be accessed using Siebel VB are set:

• AccountId
• AccountName

To access these variables, use the InvokeMethod event, and use the SetProfileAttr method to set a dynamic profile attribute. For more information about personalization, see Siebel Personalization Administration Guide.