1 / 11

Enabling Persistence of Implicit Personalizations Across Sessions using MDS

Enabling Persistence of Implicit Personalizations Across Sessions using MDS. Carmen D’Arlach April 3, 2009. Implicit Personalization. Refers to changes users make through direct manipulation. Column hide/show. Column order. Column resize. Column Freeze. ADF Change Persistence Framework.

nam
Télécharger la présentation

Enabling Persistence of Implicit Personalizations Across Sessions using MDS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enabling Persistence of Implicit Personalizations Across Sessions using MDS Carmen D’Arlach April 3, 2009

  2. Implicit Personalization • Refers to changes users make through direct manipulation Column hide/show Column order Column resize Column Freeze For Internal Use Only 2

  3. ADF Change Persistence Framework • Settings can be remembered for the duration of a session as well as across sessions using MDS. • Turned on by a setting. No coding. • Within session: No performance issues • Across sessions: Performance issues • Includes following set of component attributes Tables/Tree tables are of most concern For Internal Use Only 3

  4. General Recommendation • Enable within session at the project level. • Selectively enable across session in particular tables/tree tables. • General Guideline • Turn it on if the page is used often and users will expect it. • Turn it on if the users have a very low tolerance, i.e. comp workbench. • Factors to analyze (more details in following slides): • Saved searches • Number of columns • Frequency of use & Tolerance of user • Admin customization • Domain knowledge • But ultimately it is a strategicjudgment call to be made by PMs based on user audience and domain knowledge. For Internal Use Only 4

  5. Analysis • Saved searches include option to save the layout. • There is always a default saved search on opening the page. • Users can explicitly save the layout with their default saved search. • Seeded saved searches cannot be changed by end users. • User will have to create a new saved search and make it the default with the preferred layout settings. Saved Searches? Off yes no Large # of Columns? no Off yes Frequency of use: daily or seasonal? no Likely off yes Could be done by Admin? yes Likely off no On

  6. Analysis • All columns in the table are not visible w/o horizontal scrolling at the target resolution • A View menu is supplied that allows end users to hide/show columns Saved Searches? Off yes no Large # of Columns? Not needed no Off yes Frequency of use: daily or seasonal? no Likely off Potentially needed yes Could be done by Admin? yes Likely off no On

  7. Analysis • Frequency of use: if the user interacts with the table frequently and is likely to personalize the table • Tolerance of user: if the user is likely to have a low tolerance for re-personalizing the table, either due to the time-consuming or complex nature of the personalization and/or long periods of time between uses which make it difficult to remember the settings. For example, managers would have a low tolerance for re-personalizing the tables in Compensation Workbench each time they used it. Saved Searches? Off yes no Large # of Columns? no Off yes Frequency of use: daily or seasonal? no Likely off yes Could be done by Admin? yes Likely off no On

  8. Analysis Saved Searches? • There is a performance cost when each user makes individual personalizations. • Explicit Composer Admin customizations for targeted groups are cached and are therefore cheaper. • If the desired personalizations do not vary greatly from user to user, consider relying on Admin to make the changes for targeted groups of users instead of letting each user do it on their own. Off yes no Large # of Columns? no Off yes Frequency of use: daily or seasonal? no Likely off yes Could be done by Admin? yes Likely off no On

  9. Analysis Saved Searches? • This decision tree is a guide to help PMs do the analysis. • However, PMs do have to make the final call based on their knowledge of the domain. Off yes no Large # of Columns? no Off yes Frequency of use: daily or seasonal? no Likely off yes Could be done by Admin? yes Likely off no On

  10. How is this done? • Project level • Enable User Customizationsfor duration of session • Individual table columns • DontPersist: selected filterVisible • Persist: displayIndex frozen noWrap visible width • Ongoing investigation • Ability for admin to enable/disable out-of-box across-session persistence at customer site (Ted Farrel, Steve Miranda) • Way to make it easier for developers to configure these settings (Ken Mizuta) For Internal Use Only 10

  11. Q & Q U E S T I O N S A N S W E R S A

More Related