Performance Tuning Guide > Tuning Customer Configurations for Performance > Best Practices for User Interface Objects Layer >
Maintaining Performance When Using Applet Toggles
Applet toggles are a useful feature where multiple applets based on different business components occupy the same location in a view. Which applet displays at one time depends on a field value in a parent applet (dynamic toggle) or on a user selection (static toggle).
Dynamic toggle applets are based on the same business component, while static toggle applets may be based on different business components.
In general, when configuring applet toggles for your Siebel application, particularly dynamic toggles, you can reduce memory and CPU usage for user application sessions by minimizing the number of applet toggles and fields per applet.
It is important to be aware of potential performance impact of using applet toggles, particularly dynamic toggles:
- When a user selects a record in a parent applet for a dynamic applet toggle, the business component and fields for all of the applet toggles are instantiated and cached in memory, and all of these fields are queried.
This query is used to populate other applet toggles that may be displayed when the user changes the relevant field value in the parent record. However, each time the user selects a different record in the parent applet, all of the fields in the toggle business component are required.
Also note that view layout caching is not performed for views containing dynamic applet toggles.
- When a user navigates to a view containing a static applet toggle, the business component and fields for the default displayed applet is instantiated and cached in memory, and these fields are queried. Other business components are instantiated and cached, and other queries performed, when the user navigates to the other applets in the toggle.
In each case, cached objects remain in memory until the user navigates to a different screen.