Bookshelf Home | Contents | Index | PDF     

Siebel Personalization Administration Guide > Managing User Profiles > About Persistent User Profile Attributes >

Saving Modified Persistent Attributes

Table 7 describes saving modified persistent attributes.

Table 7. Saving Modified Persistent Attributes
If...
Then...

Persistent attributes are modified by a user and the session is updated, either directly or by the user's actions while logged in.

The modified values are not saved to the database until the session is terminated.

This is because the profile attributes are cached.

Caching profile attributes allows extremely fast access to them when building pages, while providing persistence between sessions.

Persistent attributes are modified in an administration screen and saved, for example, by a call center agent using the Profile view under the User Profile Preferences screen.

The changes are saved to the database at that time.

GetProfileAttr and Personalization

GetProfileAttr only works for fields explicitly defined in the Personalization Profile business component. GetProfileAttr does not work with system fields, which are not explicitly defined in the business component; it returns a NULL value for them.

The Id system field is an exception. This particular system field was added in order to be available to GetProfileAttr, even though it is not in the Personalization Profile business component.

    
Siebel Personalization Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.