From 368c6ac5e8ad3e1045583eb78e1db900b5acaa6e Mon Sep 17 00:00:00 2001 From: Bill Erickson Date: Tue, 29 May 2018 11:47:16 -0400 Subject: [PATCH] LP#1750894 server settings release notes Signed-off-by: Bill Erickson --- .../Client/workstation-server-settings.adoc | 40 ++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 docs/RELEASE_NOTES_NEXT/Client/workstation-server-settings.adoc diff --git a/docs/RELEASE_NOTES_NEXT/Client/workstation-server-settings.adoc b/docs/RELEASE_NOTES_NEXT/Client/workstation-server-settings.adoc new file mode 100644 index 0000000000..f94a151ccd --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Client/workstation-server-settings.adoc @@ -0,0 +1,40 @@ +Browser Client Settings & Preferences Stored on the Server +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +Browser cilent settings and preferences that should persist over time are +now stored as settings on the server. This allows settings to follow +users and workstations and reduces problems associated with losing settings +as a result of clearing browser data. + +The browser client honors setting values stored as user settings, workstation +settings, and org unit settings, depending on which setting types are +locally configured. + +Setting Types ++++++++++++++ + +* No setting can be both a user and workstation setting. They are mutually + exclusive. +* Any setting can be an org unit setting in addition to being a user or + workstaion setting. + +Read-Only Settings +++++++++++++++++++ + +Read-only settings are useful for defining values that staff can use but +not modify. For example, admins may wish to prevent users from locally +modifying the grid configuration for a given interface so it remains +consistent for all users. + +A setting is read-only when an org unit setting type exists (regardless of +whether a value is applied) and no user or workstation setting type exists. + +Upgrade Notes ++++++++++++++ + +Workstation setting types matching values previously stored in the browser +(via localStorage or Hatch) are created as part of this feature. During +upgrade, admins should consider whether any of these new setting types +should be transferred to user and/or org unit settings instead. Setting +type changes can be made at any time, but when a setting type is deleted +all of its data is deleted, so a change in type means rebuilding the data. + -- 2.11.0