Excel Integration - To Do List

Priority/Critical Items to Complete ASAP


/!\ Edit conflict - other version:


Main Design Issues (HIGH, DESIGN, AH/JS)


/!\ Edit conflict - your version:


Main Design Issues (HIGH, DESIGN, AH/JS)


/!\ End of edit conflict


  1. Able to manage multiple planning worksheets in a single workbook
  2. General design of ribbon/menu
  3. How does user create new rows?
  4. How does user copy rows?
  5. Catching exit when rows unsaved
  6. Restart revision sequence
  7. Can files be transfered between servers? (difficult: id value problems)
  8. Operations performed on all rows vs. selected rows


/!\ Edit conflict - other version:


Login/Logout (AH)

  1. Implement login flag (HIGH)

  2. Implement logout function (HIGH)

  3. Implement server select menu and default server (MEDIUM)

  4. Design for login timeout from server (HIGH, DESIGN)

  5. All dispatches should check for login flag (HIGH)

  6. Check user roles and disallow login is certain roles not present (LOW)

  7. Login in a specific contract? (LOW)


/!\ Edit conflict - your version:


Login/Logout (AH)

  1. Implement login flag (HIGH)

  2. Implement logout function (HIGH)

  3. Implement server select menu and default server (MEDIUM)

  4. Design for login timeout from server (HIGH, DESIGN)

  5. All dispatches should check for login flag (HIGH)

  6. Check user roles and disallow login is certain roles not present (LOW)

  7. Login in a specific contract? (LOW)


/!\ End of edit conflict


Attribute Lists


/!\ Edit conflict - other version:


  1. GUI for refreshing the attribute lists (HIGH, JS)

    • - Any problems if user roles change? May need to refresh user menus
  2. Need REST transaction for display status menu texts (HIGH, AH/TN)

  3. GUI side collection of display status lists (HIGH, JS)

  4. Shortening menus to restrict them to planning relevant items (LOW, WHO?)


/!\ Edit conflict - your version:


  1. GUI for refreshing the attribute lists (HIGH, JS)

    • - Any problems if user roles change? May need to refresh user menus
  2. Need REST transaction for display status menu texts (HIGH, AH/TN)

  3. GUI side collection of display status lists (HIGH, JS)

  4. Shortening menus to restrict them to planning relevant items (LOW, WHO?)


/!\ End of edit conflict


Searching


/!\ Edit conflict - other version:


  1. Order of menu items in search window (MEDIUM, AH)

  2. Handling large result sets (can wait?)
    • - GUI defines a pre-definid max limit
  3. Search by document title (MEDIUM, AH)

  4. Search by document code (MEDIUM, AH)

  5. Search by external key (MEDIUM, AH)

  6. Search by from/to revision date (MEDIUM, AH)


/!\ Edit conflict - your version:


  1. Order of menu items in search window (MEDIUM, AH)

  2. Handling large result sets (can wait?)
    • - GUI defines a pre-definid max limit
  3. Search by document title (MEDIUM, AH)

  4. Search by document code (MEDIUM, AH)

  5. Search by external key (MEDIUM, AH)

  6. Search by from/to revision date (MEDIUM, AH)


/!\ End of edit conflict


Display Data From Server


/!\ Edit conflict - other version:


  1. Merge search results with existing rows (HIGH, JS)


/!\ Edit conflict - your version:


  1. Merge search results with existing rows (HIGH, JS)


/!\ End of edit conflict


  1. See UserStatusMenusNotes:

    • - User menus based on roleId coded in header structure - Status menus based on approvalStatusListId coded in header structure


/!\ Edit conflict - other version:


  1. Delta menu (HIGH)

  2. Vorabzug flag menu (je/nein flag) (HIGH, JS)

  3. Formulas (HIGH, JS/AH)

  4. Data types and format (HIGH, JS)


/!\ Edit conflict - your version:


  1. Delta menu (HIGH)

  2. Vorabzug flag menu (je/nein flag) (HIGH, JS)

  3. Formulas (HIGH, JS/AH)

  4. Data types and format (HIGH, JS)


/!\ End of edit conflict



/!\ Edit conflict - other version:


  1. Client-side cross-field validation (HIGH, DESIGN, AH/JS)


/!\ Edit conflict - your version:


  1. Client-side cross-field validation (HIGH, DESIGN, AH/JS)


/!\ End of edit conflict



/!\ Edit conflict - other version:


  1. Document links (MEDIUM, WHO?)

    • - Grundlagen links: to a specific document

      - STN (Stellungnahme) & PRF (Pruefberichte) links: to a specific serial index prefix & number - How to handle link deletion when links changed (what to delete?)

  2. Highlighting changed but unsaved rows (HIGH, JS)

  3. Highlighting non-saved rows (HIGH, JS)


/!\ Edit conflict - your version:


  1. Document links (MEDIUM, WHO?)

    • - Grundlagen links: to a specific document

      - STN (Stellungnahme) & PRF (Pruefberichte) links: to a specific serial index prefix & number - How to handle link deletion when links changed (what to delete?)

  2. Highlighting changed but unsaved rows (HIGH, JS)

  3. Highlighting non-saved rows (HIGH, JS)


/!\ End of edit conflict


Refresh Rows


/!\ Edit conflict - other version:


  1. Refresh all vs. refresh selected (HIGH, DESIGN?, JS)

  2. Comments with cell differences (HUGH, JS)


/!\ Edit conflict - your version:


  1. Refresh all vs. refresh selected (HIGH, DESIGN?, JS)

  2. Comments with cell differences (HUGH, JS)


/!\ End of edit conflict


Editing List Data


/!\ Edit conflict - other version:


  1. Row handling and creating new rows: (HIGH, DESIGN?, AH/JS)


/!\ Edit conflict - your version:


  1. Row handling and creating new rows: (HIGH, DESIGN?, AH/JS)


/!\ End of edit conflict



/!\ Edit conflict - other version:


  1. Deleting rows should be possible
  2. Locking non-editable columns (HIGH, JS)

  3. Get next sequence number (HIGH)

    • - Client-side processing (AH) - Server-side transaction (JS)

  4. Managing doc-doc links (MEDIUM)

    • - Client-side processing (AH) - Server-side transaction (JS)


/!\ Edit conflict - your version:


  1. Deleting rows should be possible
  2. Locking non-editable columns (HIGH, JS)

  3. Get next sequence number (HIGH)

    • - Client-side processing (AH) - Server-side transaction (JS)

  4. Managing doc-doc links (MEDIUM)

    • - Client-side processing (AH) - Server-side transaction (JS)


/!\ End of edit conflict


Updating and Inserting Records


/!\ Edit conflict - other version:


  1. Save all vs. save selected (HIGH, JS)


/!\ Edit conflict - your version:


  1. Save all vs. save selected (HIGH, JS)


/!\ End of edit conflict


  1. Check for conflicts before saving (update count)
    • - Is this done by server already? - Client must not save conflicts (for whole row? or Rev by Rev?)
  2. Can same doc/rev record structure be used for both insert & update?


/!\ Edit conflict - other version:


  1. Review field mappings for doc/rev record structures (HIGH, AH)

  2. Duplicate detection (HIGH, DESIGN?, AH/JS)

    • - Partially implemented
  3. Reporting server side validation errors (HIGH, AH)

  4. Setting revision dates (HIGH, AH)

Sub-Revisions (LOW)


/!\ Edit conflict - your version:


  1. Review field mappings for doc/rev record structures (HIGH, AH)

  2. Duplicate detection (HIGH, DESIGN?, AH/JS)

    • - Partially implemented
  3. Reporting server side validation errors (HIGH, AH)

  4. Setting revision dates (HIGH, AH)

Sub-Revisions (LOW)


/!\ End of edit conflict


  1. Start new revision sequence


/!\ Edit conflict - other version:


Error Handling (MEDIUM,DESIGN?)

  1. Better reporting of details of server errors


/!\ Edit conflict - your version:


Error Handling (MEDIUM,DESIGN?)

  1. Better reporting of details of server errors


/!\ End of edit conflict


Internals


/!\ Edit conflict - other version:


  1. Named ranges (HIGH, DESIGN?, JS)

    • - Automated management - Function for repair/reset of named ranges in case of corruption - Clone worksheet - Document named ranges and their boundaries
  2. Document and revision (write) record structures

Reports

  1. Implement Bau Report (MEDIUM, JS)

Compatibility (MEDIUM)


/!\ Edit conflict - your version:


  1. Named ranges (HIGH, DESIGN?, JS)

    • - Automated management - Function for repair/reset of named ranges in case of corruption - Clone worksheet - Document named ranges and their boundaries
  2. Document and revision (write) record structures

Reports

  1. Implement Bau Report (MEDIUM, JS)

Compatibility (MEDIUM)


/!\ End of edit conflict


  1. Check with Excel 2003 - E.g. non-Ribbon version


/!\ Edit conflict - other version:


Internationalization (LOW, AH)


/!\ Edit conflict - your version:


Internationalization (LOW, AH)


/!\ End of edit conflict


  1. Convert all user display text to Consts
  2. And hard-code in German


/!\ Edit conflict - other version:


Final Cleanup and Packaging (HIGH, DESIGN, JS)


/!\ Edit conflict - your version:


Final Cleanup and Packaging (HIGH, DESIGN, JS)


/!\ End of edit conflict


  1. File packaging
    • - Document use cases - Requirement that a single file can be sent to another user - Nice if client-side and datatype checking and validation works off-line


/!\ Edit conflict - other version:


  1. Hiding of internal worksheets (header structure, etc.)


/!\ Edit conflict - your version:


  1. Hiding of internal worksheets (header structure, etc.)


/!\ End of edit conflict


  1. Hiding of system columns (key set columns) in lists

Testing


/!\ Edit conflict - other version:


  1. Test HTTPS operation


/!\ Edit conflict - your version:


  1. Test HTTPS operation


/!\ End of edit conflict


  1. Test HTTP/HTTPS proxy operation
  2. Check reading and updating of all fields
  3. Check


/!\ Edit conflict - other version:


  1. Stress testing (HIGH)

    • - Searching for long lists - Bad input data
  2. Character sets: test with Umlauts (HIGH)


/!\ Edit conflict - your version:


  1. Stress testing (HIGH)

    • - Searching for long lists - Bad input data
  2. Character sets: test with Umlauts (HIGH)


/!\ End of edit conflict


  1. Compatibility testing


/!\ Edit conflict - other version:


Refactoring (MEDIUM/LOW)


/!\ Edit conflict - your version:


Refactoring (MEDIUM/LOW)


/!\ End of edit conflict


  1. Message catalog
  2. TODO's in code


/!\ Edit conflict - other version:


Internal Documentation (LOW)


/!\ Edit conflict - your version:


Internal Documentation (LOW)


/!\ End of edit conflict


  1. Convert notes/DesignNotes into Wiki
  2. Revision sequence
  3. Named ranges
  4. URLS for REST transactions
  5. XML structures
    • - Returned records - Insert/update records


/!\ Edit conflict - other version:


User Documentation (LOW)

  1. To do in Wiki


/!\ Edit conflict - your version:


User Documentation (LOW)

  1. To do in Wiki


/!\ End of edit conflict


Copyright 2008-2014, SoftXS GmbH, Switzerland