Versions Compared

Key

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

...

  1. Get forecast name from Forecast Model, display it in Source Forecast/ Forecast Name field.
  2. Get forecast cost object name from raft.data.CostObject.COTITLE, display it in Source Forecast/ Forecast Cost Object field.
  3. Get forecast workset name from raft.data.Workset.title, display it in Source Forecast/ Forecast Workset field.
  4.  Display three radio buttons: PI, Department, Common. Put change event listener on the radio buttons.

PI Button RadioButton Clicked

  1. Show Overwrite Existing and Create New buttons. Add click listeners to both.
  2. Show Overwrite Destination Forecast in dialog. Add click listener.
  3. Display in Destination Forecast the Name of the PI, which is raft.data.CostObject.SUPERVISOR.
  4. Get forecast cost object name from raft.data.CostObject.COTITLE, display it in Destination Forecast/ Forecast Cost Object field.
  5. Wiki Markup
    Get the list of forecasts to display by searching raft.data.CostObject.Forecasts\[\] for the worksetCategory == PI. All PI Forecasts should be listed in the Destination Forecast List.
  6.  On click, call publish/share forecast with the selected forecast key as the destination scenarioKey, and the rest of the data from above as needed. Close dialog.

Department RadioButton Clicked

  1. Show Overwrite Existing and Create New buttons. Add click listeners to both.
  2. Show Overwrite Destination Forecast in dialog. Add click listener.
  3. Display in Destination Forecast the Name of the PI, which is raft.data.CostObject.SUPERVISOR.
  4. Get forecast cost object name from raft.data.CostObject.COTITLE, display it in Destination Forecast/ Forecast Cost Object field.
  5. Wiki Markup
    Get the list of forecasts to display by searching  raft.data.CostObject.Forecasts\[\] for the worksetCategory == PI. All PI  Forecasts should be listed in the Destination Forecast List.
  6.   On click, call publish/share forecast with the selected forecast key as the destination scenarioKey, and the rest of the data from above as needed. Close dialog.

Page Mockup:

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 "To Be Hired" block that contains To Be Hired templates (grad student, research assistant, research scientist, 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. 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.

...