web:accessweb2overview
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
web:accessweb2overview [2017/10/04 21:51] mikeclapp [Core functional areas] |
web:accessweb2overview [2018/07/24 19:44] (current) mjallison |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| based framework, which is now dated and doesn't follow modern conventions. A new web app | based framework, which is now dated and doesn't follow modern conventions. A new web app | ||
| is proposed to provide modern look and feel, and add expanded capabilities. | is proposed to provide modern look and feel, and add expanded capabilities. | ||
| + | |||
| + | **NOTE: This page has been superceeded by the the newest revision of WebApp stories (after 2018-07-24)** | ||
| ===== Core functional areas ===== | ===== Core functional areas ===== | ||
| Line 12: | Line 14: | ||
| * User administration (customer level) | * User administration (customer level) | ||
| * License administration (customer level) | * License administration (customer level) | ||
| + | * User profile management | ||
| Line 83: | Line 86: | ||
| * "Table" allows access to cost code page | * "Table" allows access to cost code page | ||
| * "Map" allows access to TBD | * "Map" allows access to TBD | ||
| - | * TBD: Configuration of which of the four sub-modules are displayed in the project | + | * Configuration of which of the four sub-modules are displayed in the project |
| - | * Journal | + | * Journal ([[:access:journal-file-proposal|Journal File Storage]]) |
| - | * Timeline | + | * Timeline TBD: |
| - | * Progress | + | * Progress TBD: |
| - | * Machine statistics | + | * Machine statistics TBD: |
| * TBD: Show project map for latest day, integrate with Google maps. | * TBD: Show project map for latest day, integrate with Google maps. | ||
| Line 148: | Line 151: | ||
| ===== License Administration ==== | ===== License Administration ==== | ||
| Customer admins will retain the ability the assign users to licenses, or change the maximum amount of checkout time on a license. (stretch goal: provide license event log to customers? - mja) | Customer admins will retain the ability the assign users to licenses, or change the maximum amount of checkout time on a license. (stretch goal: provide license event log to customers? - mja) | ||
| + | |||
| + | ===== User Profile Management ===== | ||
| + | Users will be able to to edit various information of their user profile, like email address and password. | ||
| + | |||
| + | The current Access page has a Logout button in the upper right of the page header. This will change to a button titled with the userid of the logged-in user, with a glyph of a user. Clicking on this button will show a menu with two options: 'USER PROFILE' and 'LOG OUT'. Clicking on LOG OUT will do the same as the current Logout button. | ||
| + | |||
| + | Clicking on USER PROFILE will post a new page which has the controls to view and edit profile information. | ||
| + | |||
| + | {{:web:accesswebstories:screen_shot_2018-06-19_at_11.33.26_am.png?400|}} | ||
| + | |||
| + | There are two main sections to this page: **User Profile** and **Assigned Keys**. | ||
| + | |||
| + | In the **User Profile** section there will be a series of labeled edit fields for the pieces of information in the user profile. In this version all but the 'Login' field will be editable, 'Login' will remain readonly. Following the series of edit fields will be buttons labeled 'Save' and 'Cancel'. Clicking on Save will validate the fields for completion and correctness, and then dismiss the page, going back to the page the user was last on. Pressing 'Cancel' will just dismiss the page and return user to the last page. A number of the labels of the edit fields are marked with an asterisk indicating these are required fields. If a user attempts to Save with one of those edit fields empty (containing only white space characters), the save operation will not complete and the user will be prompted via a message as to what needs to be done. Similarly, if the email field does not have text in valid email format, user will be prompted to correct. If the value of the Confirm Password field does not match the value of the Password field, the user will be prompted to correct. | ||
| + | |||
| + | The **Assigned Keys** section will consist of a read-only dashboard of zero or more entries of keys that the user can access. Each entry will consist of the key value and the list of applications for that key. | ||
web/accessweb2overview.1507153876.txt.gz · Last modified: 2017/10/04 21:51 by mikeclapp
Page Tools
