| 5.1 Service Evaluation
03. Local Storage | |
|---|
| 5.1.03. Local Storage: | | 1. The use of some cookies has been replaced with local storage in each persons browser. Cookies are communicated with every transaction, but local storage is only communicated upon request with a major performance improvement. | | 2. Analysis of improvement over many years shows that people are largely content with what they have, but like to tinker with some trivial details. Very few major productivity improvements have been requested, but many customisation improvements have been requested. As more customisation becomes local to each person, then higher levels of satisfaction can be achieved. |
| 2. JQUERY: | | 1. To manage the interface to local storage, the JQUERY JavaScript library has been adopted. This is a very popular proven library with acceptable overheads. | | 2. A number of other improvements are pending such as the popup mini calendar picker can be deployed. Drag and drop facilities are available and may be of value to more experienced people. |
| 3. Spreadsheets: | | 1. Every spreadsheet is highly customisable by each person to match their local needs. Every customisation of column position, filters, sorts and hidden columns was stored in a cookie and is now in local storage. |
| 4. Form: | | 1. Every form needs to be made as customisable as spreadsheets. Each field may be hidden or moved to match local needs. |
| 5. Default Values: | | 1. Every add new form needs a customisable record of default field values for each person. The add new default record key can be held in local storage to provide a customisable service. |
| 6. Options: | | 1. While most drop down list options will remain shared, some options may be customisable to match local needs. Options by system, by site and by person may be supported to give people what they want. |
| Document Control: | | 2016 Sep 16 : Latest edition as (public) page 165103. Part of common ITIL application service. |
|
|