Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

The basic idea behind this redesign is to decrease vertical scrolling and make the forecasting screen look better. By default, we will now show Forecasts and Commitments for People and Forecasts only for Expenses (because Expense Committments Commitments can not be edited, while People Commitments can be). Across the top of each forecasting block will be Show/Hide Forecasts, Show/Hide CommittmentsCommitments, and Show/Hide Actuals (as toggles where the titles change based on the state of the screen).

People Committment Commitment Rows, when changed, will have a darker color background and different icon. If the line is reverted, the "Edited" treatment is removed.

Add a Legend for the Forecast, Commitment and Actual icons.

Page Mockup: Image Added

Further details:
Image Removed Image Added
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 within it.

 
Functional Summary: On first entry, the left nav. is hidden, the name (chosen when creating) is applied and description is blank, GL blocks: People, Expenses, (further defined into subsets: M&S, Travel, Equipment, SubAwards and other) and Revenue are open, and the people are shown in their data range view. Within each block the default view is: Forecasts and Commitments for People and Forecasts only for Expenses (because Expense Commitments can not be edited, while People Commitments can be).  If the user wants, they can close or open each block of existing commitments, actuals, and forecasts.

...

Description of the Page: This page gives a user the ability to edit a particular cost object forecast. Users can add a line (person, TBH, expense or revenue) then edit it. In addition to adding new lines, users can edit existing speculations.

A forecast can be published (copied) to the following three places: the PI Workset/Scenario, the Department Workset/Scenario, or the Common/MIT ALL Scenario.

Table 1: Common User Interface Elements for the Forecasting Detail Page

This table includes all elements that appear on this page. Flag elements that have appeared on other pages.

Element

Control

Functional Description

Technical Rules

Name field

text input

User stores and edits Forecast name

Defaults to "MIT-All Forecast", key is COMMON (which is MITALL)

Show/hide forecasts,
actuals and commitments

checkbox

User clicks on it to show or hide existing commitments

Defaults to forecast checked for people, expenses, revenue blocks, commitments also checked for people

People name field

text input

User can search for person (autocomplete)

After third keydown, set timeout for 300 miliseconds, if no further keydown, execute search call  (wait until the user pauses).

Appointment field

dropdown list (select)

Until you choose a person, the only thing in the Appointment field is a dropdown that says "Choose person first." If you choose a person, the appointment field gets filled with the one or more appointments they have. If they choose a TBH, the appointment is filled in by the choice.

Disable all subsequent fields until an appointment or TBH is chosen.

Start Date

text input 

need to find out rules

Need to find out the rules (currently validates via an input mask and initial values are set)

End Date

text input 

need to find out rules

Need to find out the rules (currently validates via an input mask and initial values are set)

% (Allocation)

text input

User enters number

Required field. Floating number rounded to nearest two decimals (percentage), hidden until appointment is chosen

Pay Rate 

text input

Number populates from system once People name and Appointment is selected

Floating number rounded to nearest two decimals, hidden until appointment is chose. Should be 0 for TBH.

On Campus?

check box

User indicates if appointee is on campus. (pre-populates)


Tuition

text input

Number populates from system once Person name and Appointment is selected

Floating number locked to two decimals (money), hidden until appointment is chosen. For non-students and others, when the field is N/A, it is not editable.

All Expenses:
Expense category

dropdown list (select)

User choose an expense category from 5 options.

Required field within All Expenses. Alternatively, the category is pre-populated within the specific subset tabs.

Name field: Expenses

text input

User enters name in field

Required field.

Name field: Revenue

text input

User enters name in field

Required field.

Item cost

text input

User inputs total cost amount

Required field. Floating number locked to two decimals (money).

Rolls Off?

check box

User checks box or not

 

Revenue amount

text input

User inputs total amount

Required field. Revenue amount appears negative since it is incoming.


 

Comment

text area

User enters description. User can grow text box if wanted

Not required. Shrink text area to make inline row, let them expand it they want.

Add Row

button

Adds new forecast row of the same type below existing lines

 

Save button

button

Saves forecast to back end. Gives user Saved feedback via Growl

Always appears.

Share Button

button

Takes user to authorizations tab.

Disable button when forecast is "dirty", enable it when button is saved "clean"

Publish Button

button

Opens dialog that asks user where do they want to publish to: PI, Department or MITALL

Disable button when forecast is "dirty", enable it when button is saved "clean". See spec at top of page.

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

Valida

Message

cell A1

Lorem ipsum dolor sit amet

cell B1

Consetetur sadipscing elitr

cell C1

Sed diam nonumy eirmod tempor inviduant ut labore

cell D1

Labore et dolore magna aliquyam erat, sed diam voluptua

...

Mockup
Publish Forecast Dialogs
Publish Forecast Dialogs
1Version9
NamePublish Forecast Dialogs
Code Flow Chart for Publish Dialog:

  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. Wiki MarkupIf raft.data.CostObject.Forecasts\[\] has at least one forecast with a workset_category of Department, show these three radio buttons: PI, Department, Common, else show: PI and Common. Put change event listener on the radio buttons.

1. PI RadioButton Clicked

...

  1. Set up the source forecast information the same as we do for Publish.
  2. Make the get call to list worksets for sharing CALL WILL BE LISTED HERE. Remove the Source Workset from the list.
  3. Display the resulting list to the user.
  4. User selects one of the worksets and clicks Share Forecast.
  5. Call the standard publishForecast call with appendCO = true and the destination workset set to the one the user chose.

Version 1 Docs (deprecated)

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.

...

This table includes all elements that appear on this page. Flag elements that have appeared on other pages.

Element

Control

Functional Description

Technical Rules

Name field

text input

User stores and edits Forecast name

Defaults to "MIT-All Forecast", key is COMMON (which is MITALL)

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.

Appointment field

dropdown list (select)

Until you choose a person, the only thing in the Appointment field is "choose a person". If you choose a person, the appointment field gets filled with the one or more appointments they have. If they choose a TBH, the appointment is filled in by the choice.

Until appointment is chosen, other people fields to the right are hidden. Once appointment call to backend is made and speculation id is returned, other fields are then shown with default values from call.

Start Date

text input with calendar widget

Normal calendar widget behavior (opens auto on focus of field, can be overridden by user)

Required field. Normal Calendar widget behavior, hidden until appointment is chosen

End Date

text input with calendar widget

Normal calendar widget behavior

Required field. Normal Calendar widget behavior, hidden until appointment is chosen

Allocation

text input

User enters number

Required field. Floating number rounded to nearest two decimals (percentage), hidden until appointment is chosen

Hours per week

text input

User enters number

Required field. Floating number rounded to nearest two decimals, hidden until appointment is chosen

Tuition

text input

User enters number for tuition

Required field. Floating number locked to two decimals (money), hidden until appointment is chosen

Comment

text area

User enters description. User can grow text box if wanted

Not required. Shrink text area to make inline row, let them expand it they want.

Add Row

button

Adds new row of the same type below existing lines

 

Save button

button

 

Always appears.

Save As Button

button

 

Only active (change state from gray to active) if forecast has been saved at least once, ie not when new forecast is being created.

Revert Button

button

 

Only active (change state from gray to active) after forecast has been saved at least once.

Publish Button

button

Opens dialog that asks user where do they want to publish to: PI, Department or MITALL

 

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

Validation

Message

cell A1

Lorem ipsum dolor sit amet

cell B1

Consetetur sadipscing elitr

cell C1

Sed diam nonumy eirmod tempor inviduant ut labore

cell D1

Labore et dolore magna aliquyam erat, sed diam voluptua

...