1. Sharing and authorizations in RAFT 3 will be on worksets.
  2. Forecasts are done at the intersection of a workset and a cost object, with their authorizations coming from the "parent" workset. Therefore a user must choose a workset first, then the cost object in it, before they can create a forecast.
  3. The Common/MIT-All workset is global and all RAFT users can view it and forecast in it, but they will only see aggregate data for cost objects they do not have direct access to.
  4. To make a forecast private, a user must make their own workset, put in it the cost objects they want to forecast, then add a forecast in the context of that workset and cost object.
  5. We want to use the Chosen JavaScript Library for multi-selects. It is not great for auto-completes because it requires the elements to be present in the DOM BEFORE we can make turn a select into an autocomplete.
  6. The Advanced Search page for RAFT3 will be modeled on the advanced search from RAFT 1, but will include multi-selects.
  7. To create a Dynamic Workset, you can either create one that has a parent or one that has reference (included) worksets, but not both.
  8.  
  • No labels