[MOBILITY-557] DEV - Add the ability to save user preferences Created: 25/Mar/14  Updated: 07/Jul/14  Resolved: 07/Jul/14

Status: Closed
Project: Kuali Mobility
Component/s: Core
Affects Version/s: 3.0
Fix Version/s: 3.3

Type: Task Priority: Minor
Reporter: Joe Swanson (Inactive) Assignee: Aniruddha Jani (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 4 days
Original Estimate: 4 days

Issue Links:
Cloners
cloned to MOBILITY-704 CLONE - DEV - Add the ability to save... Open
Rely
is relied upon by MOBILITY-705 CLONE - DEV - Add the ability to load... Open
is relied upon by MOBILITY-558 DEV - Add the ability to load user pr... Closed
Rank (Obsolete): 2729
Global Rank: 82752
Sprint: Mobility 3.2

 Description   

Currently the application relies on client side management of user preferences within the application, storing data in either cookies or local storage. If the user is not authenticated, they will have to authenticate. If they are authenticated already the preferences page should display an option to save their current device preferences to their server profile. This transaction should send all configuration data to the server and store it in the UserAttribute objects within the User object.

There should be a configuration flag in kme.config.properties that allows an institution to turn this feature on and off. The values of the property should be "true" or "false" and it should be named kme.user.profile.enabled. If the value is false, the preferences screen should not display the option to save user preferences.

Items that should be saved are:
home screen information (order and visibility)
campus selection



 Comments   
Comment by Tom Amerman (Inactive) [ 07/Jul/14 ]

Cloned open part, closed this one and assigned to Aniruddha to get credit for the work

Generated at Sun Sep 20 09:17:50 CDT 2020 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.