Enabling Persistence of Implicit Personalizations Across Sessions using MDS Carmen D’Arlach April...
-
Upload
myles-gordon -
Category
Documents
-
view
216 -
download
2
Transcript of Enabling Persistence of Implicit Personalizations Across Sessions using MDS Carmen D’Arlach April...
<Insert Picture Here>
Enabling Persistence of Implicit Personalizations Across Sessions using MDSCarmen D’ArlachApril 3, 2009
Implicit Personalization
• Refers to changes users make through direct manipulation
For Internal Use Only 2
Column order Column hide/show
Column FreezeColumn resize
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
For Internal Use Only 3
Tables/Tree tables are of most concern
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 strategic judgment call to be made by PMs based on user audience and domain knowledge.
For Internal Use Only 4
Analysis
Saved Searches?
Saved Searches?
Large # of Columns?
Large # of Columns?
Frequency of use: daily or seasonal?
Frequency of use: daily or seasonal?
yes
no
yes
no
no
OffOff
OffOff
yes
Could be doneby Admin?
Could be doneby Admin?
no
yes
Likely offLikely off
Likely offLikely off
OnOn
•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.
Analysis
Saved Searches?
Saved Searches?
Large # of Columns?
Large # of Columns?
Frequency of use: daily or seasonal?
Frequency of use: daily or seasonal?
yes
no
yes
no
no
OffOff
OffOff
yes
Could be doneby Admin?
Could be doneby Admin?
no
yes
Likely offLikely off
Likely offLikely off
OnOn
• 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
Not neededNot needed
Potentially neededPotentially needed
Analysis
Saved Searches?
Saved Searches?
Large # of Columns?
Large # of Columns?
Frequency of use: daily or seasonal?
Frequency of use: daily or seasonal?
yes
no
yes
no
no
OffOff
OffOff
yes
Could be doneby Admin?
Could be doneby Admin?
no
yes
Likely offLikely off
Likely offLikely off
OnOn
• 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.
Analysis
Saved Searches?
Saved Searches?
Large # of Columns?
Large # of Columns?
Frequency of use: daily or seasonal?
Frequency of use: daily or seasonal?
yes
no
yes
no
no
OffOff
OffOff
yes
Could be doneby Admin?
Could be doneby Admin?
no
yes
Likely offLikely off
Likely offLikely off
OnOn
• 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.
Analysis
Saved Searches?
Saved Searches?
Large # of Columns?
Large # of Columns?
Frequency of use: daily or seasonal?
Frequency of use: daily or seasonal?
yes
no
yes
no
no
OffOff
OffOff
yes
Could be doneby Admin?
Could be doneby Admin?
no
yes
Likely offLikely off
Likely offLikely off
OnOn
• 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.
How is this done?
• Project level• Enable User Customizations
for 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
AQ&Q U E S T I O N SQ U E S T I O N S
A N S W E R SA N S W E R S