Excel Integration - To Do List

• Back

Priority/Critical Items to Complete ASAP

• Fix writing of title fields - should write to all revisions

• JS - Fix handling of named ranges

  • Ability to change between Bau & Bau2 without having to exit and restart Excel

• JS - Implement user role menus

• AH - Cleanup VBA code formatting

• AH - Cleanup layout sheet in in Lib, change yellow cells to appropriate gray color

• AH - Implement display of user defined fields after search

  • Fix paths in header structure

  • Add case for handling user defined fields

• AH - Implement global login flag

Main Design Issues

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

Login/Logout

1. Implement login flag
2. Implement logout function
3. Implement server select menu and default server
4. Design for login timeout from server
5. All dispatches should check for login flag
6. Check user roles and disallow loging is certain roles not present
7. Login in a specific contract?

Attribute Lists

1. GUI for refreshing the attribute lists
   • - Any problems if user roles change? May need to refresh user menus
2. Need REST transaction for display status menu texts
3. GUI side collection of display status lists
4. Shortening menus to restruct them to planning revelant items

Searching

1. Order of menu items in search window
2. Handling large result sets (can wait?)
   • - GUI defines a pre-definid max limit
3. Search by document title
4. Search by document code
5. Search by external key
6. Search by from/to revision date

Display Data From Server

1. Merge search results with existing rows

2. See UserStatusMenusNotes:

   • - User menus based on roleId coded in header structure - Status menus based on approvalStatusListId coded in header structure
3. Delta menu
4. Vorabzug flag menu (je/nein flag)
5. Formulas
6. Data types and format
   • - Dates - Numbers - Implement rules
7. Client-side cross-field validation
   • - Define rules - Complete date and status - Sequence of complete dates - sequence of plan dates
8. Document links
   • - Grundlagen links: to a specific document

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

9. Highlighting changed but unsaved rows
10. Highlighting non-saved rows

Refresh Rows

1. Refresh all vs. refresh selected
2. Comments with cell differences

Editing List Data

1. Row handling and creating new rows:
   • - How to create new rows: via menu or copy paste?
     • - Insert at end of list - Insert at current position
     - Default delta values for new rows? - Users should be able to sort/rearrange rows

     - Is copy & past possible? - Can fill down be used? xpo would really link it

     • - What happens in menu columns?
2. Deleting rows should be possible
3. Locking non-editable columns
4. Get next sequence number
   • - Client-side processing - Server-side transaction
5. Managing doc-doc links
   • - Client-side processing - Server-side transaction

Updating and Inserting Records

1. Save all cs. save selected
2. 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?)

3. Can same doc/rev record structure be used for both insert & update?

4. Review field mappings for doc/rev record structures
5. Duplicate detection
6. Partially implemented
7. Reporting server side validation errors
8. Setting revision dates (via doc

Sub-Revisions

1. Start new revision sequence

Error Handling

1. Reporting details of server errors

Internals

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

Implement Bau Report

Compatibility

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

Internationalization

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

Final Cleanup and Packaging

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
2. Hiding of internal wotksheets (header structure, etc.)
3. Hiding of system columns (key set columns) in lists

Testing

1. Test HTTPS opertation
2. Test HTTP/HTTPS proxy operation
3. Check reading and updating of all fields
4. Check
5. Stress testing
   • - Searching for long lists - Bad input data
6. Character sets: test with Umlauts
   • - Test Umlauts in UTF-8 set to server - Test Umlauts in ISO-8859-1 set from server
7. Compatibility testing

Refactoring

1. Message catalog
2. TODO's in code

Internal Documentation

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

User Documentation

1. To do in Wiki