Saving Modified Persistent Attributes

The following table describes 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.