User Tools

Site Tools


web:accessweb2overview

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
web:accessweb2overview [2017/06/19 16:41]
mjallison [Access Client]
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
 +
 +
 +===== Revised Actual File Screens 10-4-2017 =====
 +
 +The web file app is functionally complete and we're working on visual refinement. This is a pass on visual changes to the actual page.
 +
 +{{:​web:​file_screen_revision_10-4-2017.png?​600|}}
 +
 +Revisions in Red (L=leftalign,​ R=rightalign,​ FR=Float:​Right,​ C=Center
 +{{:​web:​file_screen_revision_10-4-2017_diif.png?​600|}}
 +
 +I tried to do a very light touch on the css. If for some reason you need it for reference it's available here:​[[http://​www.agtek.com/​css/​access.css|External Link]]
 +
  
  
Line 44: Line 60:
 ===== Project Management ===== ===== Project Management =====
 Project management is the synthesis of several project aspects of project related data contained in the Access server: Project management is the synthesis of several project aspects of project related data contained in the Access server:
-  * Tracks (auto tracking via vehicles)+  * "​Machine ​Tracks" ​(auto tracking via vehicles)
   * Photos   * Photos
-  * User tracks ​(need better name)+  * "User tracks"
   * Measure areas   * Measure areas
   * Notes   * Notes
Line 54: Line 70:
 references to the previously mentioned data items, and the journal may be displayed as part of the project references to the previously mentioned data items, and the journal may be displayed as part of the project
 summary. Items to note are listed after this image: summary. Items to note are listed after this image:
 +
 {{:​web:​accesswebstories:​accessprojects.png?​600|Projects overview}} {{:​web:​accesswebstories:​accessprojects.png?​600|Projects overview}}
   * Projects overview has 3 different sorting bands: Today, Yesterday, Other days   * Projects overview has 3 different sorting bands: Today, Yesterday, Other days
Line 69: 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
 +  * Configuration of which of the four sub-modules are displayed in the project
 +    * Journal ([[:​access:​journal-file-proposal|Journal File Storage]])
 +    * Timeline TBD: 
 +    * Progress TBD: 
 +    * Machine statistics TBD: 
 +  * TBD: Show project map for latest day, integrate with Google maps.
  
 Clicking on the project opens the day detail for that day. This image shows an example day detail view: Clicking on the project opens the day detail for that day. This image shows an example day detail view:
 +(NB: The four buttons on the left are a story board artifact and not in the actual implementation)
 +
 {{:​web:​accesswebstories:​accessprojectdaydetail.png?​600|Single project day detail}} {{:​web:​accesswebstories:​accessprojectdaydetail.png?​600|Single project day detail}}
   * Each track for the day is listed with it's time line view, the vehicle name, the actual time range, and operations.   * Each track for the day is listed with it's time line view, the vehicle name, the actual time range, and operations.
Line 86: Line 111:
   * A "​create project"​ summary card is inserted into the display. ​   * A "​create project"​ summary card is inserted into the display. ​
   * User can specify the project name and description (text fields), timezone, and code list.    * User can specify the project name and description (text fields), timezone, and code list. 
 +  * This should have the configuration checkboxes here for the four project sub-cards.
  
  
 Pressing the CostCodeList button allows the user to edit cost codes: Pressing the CostCodeList button allows the user to edit cost codes:
 {{:​web:​accesswebstories:​costcodes.png?​600|Cost Code base page}} {{:​web:​accesswebstories:​costcodes.png?​600|Cost Code base page}}
 +
 All known cost code lists are listed in the upper portion of the left hand pane. Below the pane are buttons for creating a new CostList, editing, and deleting the cost list. All known cost code lists are listed in the upper portion of the left hand pane. Below the pane are buttons for creating a new CostList, editing, and deleting the cost list.
 +  * Edit boxes at top are for adding new items. Use a "​+"​ button to left and it should appear like the "new machine"​ does.
 +  * Left hand pencil, "​Edit"​ allows user to edit the list name.
 +  * 
 ===== Vehicle and Tracker Management ===== ===== Vehicle and Tracker Management =====
 The web app provides the ability to create new vehicle descriptions and assign them to trackers and projects. Vehicles provide a descriptive capability to the actual work done in the project. When combined with cost codes The web app provides the ability to create new vehicle descriptions and assign them to trackers and projects. Vehicles provide a descriptive capability to the actual work done in the project. When combined with cost codes
Line 111: Line 141:
     * The quantity may be changed.     * The quantity may be changed.
   * Machines are sorted by project   * Machines are sorted by project
-  * TBD: Other sorting option (ST support sort by type). +  * TBD: Menu option: Other sorting option (ST support sort by type). 
-  * TBD: Show inactive... ​+  * TBD: Menu option: Show inactive... ​
  
  
Line 121: 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.1497890473.txt.gz · Last modified: 2017/06/19 16:41 by mjallison