Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Page Layout: This page consists of a main grid/form for forecasting, a forecasting totals block that follows the user as they scroll down, and a "favorites" block that contains To Be Hired templates (grad student, research assistant, research scientist, etc.) and any spending favorites (trip to Provence in Spring, etc.). The forecasting form/grid is further broken down into GL sections, one for each of the high level CEMIT or Approved GLS. Each GL block contains a subtotals block at the bottom.
 
Functional Summary: On first entry, the left nav is hidden, the name and description are blank, all GL blocks are open, and the people are shown in their data range view. If the user wants, they can close each block of existing commitments. (Do we need a close all/open all button???) Above each existing commitment in each GL block is an empty row so users can immediately begin forecasting. When a user gets to the last input field in the row, a new blank row is automatically added. In addition and not shown in the image is a "Add new row" button on each block. If a user wants to add a To Be Hired, they click on them and a new row is added that contains the defaults from the To Be Hired they clicked on, which can then be edited.

...

Element

Control

Functional Description

Technical Rules

cell A1

cell A2

cell A3

cell A4

cell B1

cell B2

cell B3

cell B4

cell C1

cell C2

cell C3

cell C4

Name field

text input

User stores and edits Forecast name


Show's actuals and commitments

checkbox

User clicks on it to show and hide existing commitments

Defaults to checked, should be placed closer to grid it controls

Show/Hide Accordion

button

Shows and hides all commitments in GL block

Overrideable by the Show Actuals and Commitments checkbox (if user hides people block, clicks hide all, then clicks show all, people block is visible)

Person name field

text input

User can search for person (autocomplete) including TBHs

After third keydown, set timeout for 300 miliseconds, if no further keydown, execute search call  (wait until the user pauses). Make timeout length a setting, let us play with it, hide setting for January release and default to best guess. Show default if users complain.

 

 

 

 

cell D1

cell D2

cell D3

cell D4

Wiki Markup
*Table X:* *Validation Rules for \[name of page\] Page*

...