Bookshelf Home | Contents | Index | Search | PDF

Configuration Guidelines > Configuring the User Interface >

Personalization

---

You can use personalization to increase user satisfaction. However, excessive personalization can have a negative impact on performance. The following guidelines apply to personalization when configuring your application:

Test personalization rules thoroughly to make sure that they do not override your application's desired behavior.
Do not use personalization to replace standard visibility and the use of search specifications on business components or applets.
Avoid using personalization to trigger general validation scripts or to invoke custom methods that implement application logic. This functionality should be confined to the Business Objects layer through standard configuration techniques or scripting.
Carefully manage the profile attributes set in a given session. Maintain personalization rules using the Personalization Administration and Runtime Events Administration screens. Setting attribute values through scripting in the repository could result in conflicts and unexpected behavior.
Using SetProfileAttr and GetProfileAttr can be effective for reasons other than storing user profile information. For example, calculated fields can use expressions containing GetProfileAttr. Search specifications can also use expressions with GetProfileAttr. Profile attributes in this case are global variables stored in the application, so they need to be documented and appropriately managed in order to avoid conflicts and errors.

Bookshelf Home | Contents | Index | Search | PDF