Dong Shin 08.12.2014

  • working on adding Planned Baseline rows
    • added Planned Obligation Baseline: and Planned Outlay Baseline: to obligation_outlay_types table
      • INSERT INTO `project_portfolio_enh`.`obligation_outlay_types` (`uid`, `type`, `visible`, `status`) VALUES (NULL, ‘Planned Obligation Baseline:’, NULL, NULL), (NULL, ‘Planned Outlay Baseline:’, NULL, NULL);
    • add Planned Obligation/Outlay Baseline rows for existing data
      • INSERT INTO obligations_outlays
        (type, year, year_count, project_id, funding_id)
        (SELECT ‘Planned Obligation Baseline:’, year, year_count, project_id, funding_id FROM `obligations_outlays`
        GROUP BY funding_id, year_count) UNION ALL
        (SELECT ‘Planned Outlay Baseline:’, year, year_count, project_id, funding_id FROM `obligations_outlays`
        GROUP BY funding_id, year_count);
    • update visible in obligation_outlay_types so only Admins and NSA PM’s can see the planned baseline rows
      • UPDATE obligation_outlay_types SET visible = 0;
        UPDATE obligation_outlay_types SET visible = 1 WHERE type <> ‘Planned Obligation Baseline:’
        AND type <> ‘Planned Outlay Baseline:’;
    • added visible flag to getFinancialData
  • back up current database – project_portfolio_enh_081214, cleaned up databases….

Phil 8.7.14

8:00 – 5:00 SR

  • DB Backups – done
  • Deploy new FR app – done
  • Update index page with link and description – done
  • Removed “Update” button for a while
  • Need to add top and bottom marking <div>
  • Add delete FR and delete row functionality to client
  • Update should “add” if there are no rows
  • Make sure that the year is greater  or equal to today – done
  • Add validators to update
  • Add logger – done
  • Send error message back to client for alert.
  • Make sure that date parser is correct – may need to add one to month – done
  • leave ‘@’ in string validator – done
  • Add default zeros in number fields – done
  • Realized that using delete/add would cause artifacts in the DB, changed it so that the table has the old funding request deleted before the new one is added.

Phil 8.6.14

8:00 – 6:00 SR

  • Woke up at 3:30 thinking about the loading problem. Thoughts are in the previous entry.
  • Deployed the new version, which went nicely.
  • Discovered a problem with IE8. Comments (//) in the <style> section don’t work, and the following needs to be added to the .panelButton style:
    • display: inline-block;
    • float: left;
  • Onward…
  • Made all the changes to FundingRequestPanel and things are working. Still need to add the adjustment of the fr_master_table for Submit. If the testing works out, then things are kind of beta?
  • Add deleteRow() and deleteFR() to java. Done
  • Integrated new save

Phil 8.5.14

8:00 – 6:00 SR

  • Submit button
  • Clear button – done
  • Why are the buttons turning yellow on load? State issues. Fixed
  • Check to see that users are not being changed on save.
  • Disable access to dropdown and remove NA from list – done
  • The Submit and changed users are the result of the data about a funding request (name, approval) are being saved in the FundingRequestPanel as part of each submission. There needs to be a fr_master_table:
    • uid: hash of frName and login
    • frName
    • status
  • This table will be used by FundingRequestPanel (FRP) only, and the FRP will not be stored in the fr_panel_table. Rows will not be kept in the table. Instead, the rows will be reconstituted. This means that a lot of the base class functionality (_fromArray(), _toJson()) will have to be rewritten to access the new table. Login will read from this table and if there is data to load, then the FRP will show. Maybe show it anyway, with a “New” button that fires a “FundingRequestPanel:clear” event.

Phil 8.4.14

8:00 – 2:30 SR

  • Add non-admin viewing logic to server code – done
  • Add ability to select requests by status (incomplete, submitted, rejected accepted) to req panel, then clear and re-run the query
  • Add submit functionality.
  • Set status to green when NA is selected.
  • Get the latest YUI-base for deployment and test – done
  • Make sure that the DB creation files are correct. – done
  • Make sure that the original user’s information is being saved when updated by Admin – done
  • Check https functionality.
  • Zip up and try deploying!
  • Fixed some bugs in the assembling of the queries. Also had to add a regex

Phil 8.1.14

8:00 – 5:30 SR

  • DB and webapps backup
  • Deployed new FA, but had to roll back because the FMPs were broken
  • Working on getting all the login permutations handled.
    • Added status return if no entries found.
    • Added fr_name parameter to the getPanel call.
  • Built the load query
  • Added a method that iterates through the array of results and builds the panel from that
  • Hooked op the FundingRequestPanel to the fromArray() method and connected it to the login. I still need to adjust the behavior based on whether the role is admin, but it works.
  • Added a load event to FundingRequestPanel
  • Added a method to grab the array of results and feed it to all the panels except FundingRequestPanel.
  • Tested and wporking for one funding request and the Administrator role.

Saved out and loaded in from the DB:

woohoo

Phil 7.31.14

8:00 – 5:00

  • Deployed new FA, RA
  • DB Backups.
  • Changed the query in the truancy report because SUM(0, null) != 0 + null in MySQL
  • Got the query built to construct a single response from the master/date/number/text tables :
    • select fpt.gid, fpt.panel_name, fpt.field_name, ftt.value from fr_panel_table fpt right
      join fr_text_table ftt on fpt.uid = ftt.uid where login = ‘projportfolio’ and panel_name =
      ‘fundingRequestsPanel’
      union
      select fpt.gid, fpt.panel_name, fpt.field_name, ftt.value from fr_panel_table fpt right
      join fr_number_table ftt on fpt.uid = ftt.uid where login = ‘projportfolio’ and panel_name
      = ‘fundingRequestsPanel’
      union
      select fpt.gid, fpt.panel_name, fpt.field_name, ftt.value from fr_panel_table fpt right
      join fr_date_table ftt on fpt.uid = ftt.uid where login = ‘projportfolio’ and panel_name =
      ‘fundingRequestsPanel’;
  • Getting the fundingRequestTable back with the login info
  • For tomorrow
    • Populate funding request panel
    • Populate other panels on load
    • Submit changes status and just saves, I think
    • Change the YUI library to point at a local copy
    • Zip and deploy???

 

Phil 7.30.14

8:00 – 5:00 SR

  • DB backups
  • New FA. There does seem to be a problem with the calculation for cell colors
  • Continuing with writing to the DB from the JS client
  • Chased down a bunch of bugs having to do with the way that fields were being loaded, particularly on the Funding Panel, where items are represented by sourceDivs
  • Set up the table structure so that guids are produced for each row on the client then used to match between the master table and the String/data/number tables.
  • Added the code to the servlet that inserts data, but haven’t connected it to the DB yet. Tomorrow.

Phil 7.29.14

8:00 – 5:00 SR

  • DB Backups
  • Wound up having to write a class that allows for the traversal of a JSON object, which I was not expecting and added a day to the effort. It’s based on the code up at json.org. Finished with the basics, and can recursively navigate and return key/value pairs or an array of Objects that match a given key. Tomorrow we’ll need to add capability (either to the JsonNav class or to the servlet that will write rows into the db.

Dong Shin 07.28.2014

  • deployed new FA with Req’s by Project queries
    • found that Query Builder adds where and group by clause – fixed
    • not saving queries – fixed
    • percent values should be calculated using Total Budgets, not Committed Amounts  – fixed
  • working on summarizing obligations, outlays, pm actuals for Req’s by Project queries