Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Personalization Administration Guide > User Profiles > User Profile Attributes >
Dynamic User Profile Attributes
Dynamic attributes are created at run time and are not based on any business component fields. They are session specific.
Dynamic attributes are set and modified by actions the user takes while navigating the system, and are never written to the database. They allow real-time modification of the user experience. They are related to the state of the user, as determined when he or she entered the application.
The login process can also automatically enter dynamic attributes. The following dynamic profile attributes are set by the system at run time:
Dynamic Profile Attribute Possible Values IsStandaloneWebClient "TRUE" or "FALSE" IsAnonymous "TRUE" or "FALSE" ApplicationName Name of the application ActiveViewName Name of the active viewDynamic attributes are retrieved the same way as persistent attributes, using
GetProfileAttr()
. If the attribute is not set (or does not exist) for a given user, it will return nothing, but will not give an error message.Dynamic profile attributes can be different for each user. When a dynamic profile attribute is set, it exists for that user only. This works because of how dynamic attributes are set and retrieved: no errors occur if an administrator references dynamic attributes that do not exist. If a dynamic profile attribute does not exist and the user sets it, a new one is created.
NOTE: The ActiveViewName profile attribute is set after the user has been navigated to the view.
The following are examples of the usage of dynamic profile attributes:
GetProfileAttr("AttrDoesNotExist")
returns NULL.SetProfileAttr("NewAttribute","value")
creates a new dynamic profile attribute.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Personalization Administration Guide Published: 18 April 2003 |