Deletions are marked like this. | Additions are marked like this. |
Line 25: | Line 25: |
---- /!\ '''Edit conflict - other version:''' ---- | |
Line 27: | Line 26: |
---- /!\ '''Edit conflict - your version:''' ---- = Main Design Issues (HIGH, DESIGN, AH/JS) = ---- /!\ '''End of edit conflict''' ---- |
|
Line 43: | Line 37: |
---- /!\ '''Edit conflict - other version:''' ---- | |
Line 54: | Line 47: |
---- /!\ '''Edit conflict - your version:''' ---- = Login/Logout (AH) = 1. Implement login flag '''(HIGH)''' 1. Implement logout function '''(HIGH)''' 1. Implement server select menu and default server '''(MEDIUM)''' 1. Design for login timeout from server '''(HIGH, DESIGN)''' 1. All dispatches should check for login flag '''(HIGH)''' 1. Check user roles and disallow login is certain roles not present '''(LOW)''' 1. Login in a specific contract? '''(LOW)''' ---- /!\ '''End of edit conflict''' ---- |
|
Line 70: | Line 50: |
---- /!\ '''Edit conflict - other version:''' ---- | |
Line 77: | Line 56: |
---- /!\ '''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 1. Need REST transaction for display status menu texts '''(HIGH, AH/TN)''' 1. GUI side collection of display status lists '''(HIGH, JS)''' 1. Shortening menus to restrict them to planning relevant items '''(LOW, WHO?)''' ---- /!\ '''End of edit conflict''' ---- |
|
Line 88: | Line 59: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 92: | Line 61: |
- GUI defines a pre-definid max limit | - GUI defines a pre-defined max limit |
Line 98: | Line 67: |
---- /!\ '''Edit conflict - your version:''' ---- 1. Order of menu items in search window '''(MEDIUM, AH)''' 1. Handling large result sets (can wait?) - GUI defines a pre-definid max limit 1. Search by document title '''(MEDIUM, AH)''' 1. Search by document code '''(MEDIUM, AH)''' 1. Search by external key '''(MEDIUM, AH)''' 1. Search by from/to revision date '''(MEDIUM, AH)''' ---- /!\ '''End of edit conflict''' ---- |
|
Line 112: | Line 70: |
---- /!\ '''Edit conflict - other version:''' ---- | |
Line 114: | Line 71: |
---- /!\ '''Edit conflict - your version:''' ---- 1. Merge search results with existing rows '''(HIGH, JS)''' ---- /!\ '''End of edit conflict''' ---- |
|
Line 122: | Line 74: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 128: | Line 78: |
---- /!\ '''Edit conflict - your version:''' ---- 1. Delta menu '''(HIGH)''' 1. Vorabzug flag menu (je/nein flag) '''(HIGH, JS)''' 1. Formulas '''(HIGH, JS/AH)''' 1. Data types and format '''(HIGH, JS)''' ---- /!\ '''End of edit conflict''' ---- |
|
Line 139: | Line 81: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 142: | Line 82: |
---- /!\ '''Edit conflict - your version:''' ---- 1. Client-side cross-field validation '''(HIGH, DESIGN, AH/JS)''' ---- /!\ '''End of edit conflict''' ---- |
|
Line 151: | Line 86: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 160: | Line 93: |
---- /!\ '''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?) 1. Highlighting changed but unsaved rows '''(HIGH, JS)''' 1. Highlighting non-saved rows '''(HIGH, JS)''' ---- /!\ '''End of edit conflict''' ---- |
|
Line 172: | Line 95: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 177: | Line 98: |
---- /!\ '''Edit conflict - your version:''' ---- 1. Refresh all vs. refresh selected '''(HIGH, DESIGN?, JS)''' 1. Comments with cell differences '''(HUGH, JS)''' ---- /!\ '''End of edit conflict''' ---- |
|
Line 185: | Line 100: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 188: | Line 101: |
---- /!\ '''Edit conflict - your version:''' ---- 1. Row handling and creating new rows: '''(HIGH, DESIGN?, AH/JS)''' ---- /!\ '''End of edit conflict''' ---- |
|
Line 199: | Line 107: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 212: | Line 118: |
---- /!\ '''Edit conflict - your version:''' ---- - Can fill down be used? Axpo would really link it - What happens in menu columns? 1. Deleting rows should be possible 1. Locking non-editable columns '''(HIGH, JS)''' 1. Get next sequence number '''(HIGH)''' - Client-side processing '''(AH)''' - Server-side transaction '''(JS)''' 1. Managing doc-doc links '''(MEDIUM)''' - Client-side processing '''(AH)''' - Server-side transaction '''(JS)''' ---- /!\ '''End of edit conflict''' ---- |
|
Line 228: | Line 120: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 231: | Line 121: |
---- /!\ '''Edit conflict - your version:''' ---- 1. Save all vs. save selected '''(HIGH, JS)''' ---- /!\ '''End of edit conflict''' ---- |
|
Line 240: | Line 125: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 250: | Line 133: |
---- /!\ '''Edit conflict - your version:''' ---- 1. Review field mappings for doc/rev record structures '''(HIGH, AH)''' 1. Duplicate detection '''(HIGH, DESIGN?, AH/JS)''' - Partially implemented 1. Reporting server side validation errors '''(HIGH, AH)''' 1. Setting revision dates '''(HIGH, AH)''' = Sub-Revisions (LOW) = ---- /!\ '''End of edit conflict''' ---- |
|
Line 263: | Line 135: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 269: | Line 139: |
---- /!\ '''Edit conflict - your version:''' ---- = Error Handling (MEDIUM,DESIGN?) = 1. Better reporting of details of server errors ---- /!\ '''End of edit conflict''' ---- |
|
Line 278: | Line 141: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 293: | Line 154: |
---- /!\ '''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 1. Document and revision (write) record structures = Reports = 1. Implement Bau Report '''(MEDIUM, JS)''' = Compatibility (MEDIUM) = ---- /!\ '''End of edit conflict''' ---- |
|
Line 311: | Line 156: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 314: | Line 157: |
---- /!\ '''Edit conflict - your version:''' ---- = Internationalization (LOW, AH) = ---- /!\ '''End of edit conflict''' ---- |
|
Line 323: | Line 161: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 327: | Line 163: |
---- /!\ '''Edit conflict - your version:''' ---- = Final Cleanup and Packaging (HIGH, DESIGN, JS) = ---- /!\ '''End of edit conflict''' ---- |
|
Line 337: | Line 167: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 340: | Line 168: |
---- /!\ '''Edit conflict - your version:''' ---- 1. Hiding of internal worksheets (header structure, etc.) ---- /!\ '''End of edit conflict''' ---- |
|
Line 349: | Line 172: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 352: | Line 173: |
---- /!\ '''Edit conflict - your version:''' ---- 1. Test HTTPS operation ---- /!\ '''End of edit conflict''' ---- |
|
Line 359: | Line 175: |
1. Check ---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 366: | Line 179: |
---- /!\ '''Edit conflict - your version:''' ---- 1. Stress testing '''(HIGH)''' - Searching for long lists - Bad input data 1. Character sets: test with Umlauts '''(HIGH)''' ---- /!\ '''End of edit conflict''' ---- |
|
Line 378: | Line 183: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 381: | Line 184: |
---- /!\ '''Edit conflict - your version:''' ---- = Refactoring (MEDIUM/LOW) = ---- /!\ '''End of edit conflict''' ---- |
|
Line 390: | Line 188: |
---- /!\ '''Edit conflict - other version:''' ---- |
|
Line 393: | Line 189: |
---- /!\ '''Edit conflict - your version:''' ---- = Internal Documentation (LOW) = ---- /!\ '''End of edit conflict''' ---- |
|
Line 408: | Line 199: |
---- /!\ '''Edit conflict - other version:''' ---- | |
Line 412: | Line 202: |
---- /!\ '''Edit conflict - your version:''' ---- = User Documentation (LOW) = 1. To do in Wiki ---- /!\ '''End of edit conflict''' ---- |
Excel Integration - To Do List
Contents
- Excel Integration - To Do List
- Priority/Critical Items to Complete ASAP
- Main Design Issues (HIGH, DESIGN, AH/JS)
- Login/Logout (AH)
- Attribute Lists
- Searching
- Display Data From Server
- Refresh Rows
- Editing List Data
- Updating and Inserting Records
- Sub-Revisions (LOW)
- Error Handling (MEDIUM,DESIGN?)
- Internals
- Reports
- Compatibility (MEDIUM)
- Internationalization (LOW, AH)
- Final Cleanup and Packaging (HIGH, DESIGN, JS)
- Testing
- Refactoring (MEDIUM/LOW)
- Internal Documentation (LOW)
- User Documentation (LOW)
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 (HIGH, DESIGN, AH/JS)
- Able to manage multiple planning worksheets in a single workbook
- General design of ribbon/menu
- How does user create new rows?
- How does user copy rows?
- Catching exit when rows unsaved
- Restart revision sequence
- Can files be transfered between servers? (difficult: id value problems)
- Operations performed on all rows vs. selected rows
Login/Logout (AH)
Implement login flag (HIGH)
Implement logout function (HIGH)
Implement server select menu and default server (MEDIUM)
Design for login timeout from server (HIGH, DESIGN)
All dispatches should check for login flag (HIGH)
Check user roles and disallow login is certain roles not present (LOW)
Login in a specific contract? (LOW)
Attribute Lists
GUI for refreshing the attribute lists (HIGH, JS)
- - Any problems if user roles change? May need to refresh user menus
Need REST transaction for display status menu texts (HIGH, AH/TN)
GUI side collection of display status lists (HIGH, JS)
Shortening menus to restrict them to planning relevant items (LOW, WHO?)
Searching
Order of menu items in search window (MEDIUM, AH)
- Handling large result sets (can wait?)
- - GUI defines a pre-defined max limit
Search by document title (MEDIUM, AH)
Search by document code (MEDIUM, AH)
Search by external key (MEDIUM, AH)
Search by from/to revision date (MEDIUM, AH)
Display Data From Server
Merge search results with existing rows (HIGH, JS)
See UserStatusMenusNotes:
- - User menus based on roleId coded in header structure - Status menus based on approvalStatusListId coded in header structure
Delta menu (HIGH)
Vorabzug flag menu (je/nein flag) (HIGH, JS)
Formulas (HIGH, JS/AH)
Data types and format (HIGH, JS)
- - Dates - Numbers - Implement rules
Client-side cross-field validation (HIGH, DESIGN, AH/JS)
- - Define rules - Complete date and status - Sequence of complete dates - sequence of plan dates
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?)
- - Grundlagen links: to a specific document
Highlighting changed but unsaved rows (HIGH, JS)
Highlighting non-saved rows (HIGH, JS)
Refresh Rows
Refresh all vs. refresh selected (HIGH, DESIGN?, JS)
Comments with cell differences (HUGH, JS)
Editing List Data
Row handling and creating new rows: (HIGH, DESIGN?, AH/JS)
- - How to create new rows: via menu or copy paste?
- - Insert at end of list - Insert at current position
- Is copy & past possible? - Can fill down be used? Axpo would really link it
- - What happens in menu columns?
- - How to create new rows: via menu or copy paste?
- Deleting rows should be possible
Locking non-editable columns (HIGH, JS)
Get next sequence number (HIGH)
- Client-side processing (AH) - Server-side transaction (JS)
Managing doc-doc links (MEDIUM)
- Client-side processing (AH) - Server-side transaction (JS)
Updating and Inserting Records
Save all vs. save selected (HIGH, JS)
- 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?)
Can same doc/rev record structure be used for both insert & update?
Review field mappings for doc/rev record structures (HIGH, AH)
Duplicate detection (HIGH, DESIGN?, AH/JS)
- - Partially implemented
Reporting server side validation errors (HIGH, AH)
Setting revision dates (HIGH, AH)
Sub-Revisions (LOW)
- Start new revision sequence
Error Handling (MEDIUM,DESIGN?)
- Better reporting of details of server errors
Internals
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
- Document and revision (write) record structures
Reports
Implement Bau Report (MEDIUM, JS)
Compatibility (MEDIUM)
- Check with Excel 2003 - E.g. non-Ribbon version
Internationalization (LOW, AH)
- Convert all user display text to Consts
- And hard-code in German
Final Cleanup and Packaging (HIGH, DESIGN, JS)
- 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
- Hiding of internal worksheets (header structure, etc.)
- Hiding of system columns (key set columns) in lists
Testing
- Test HTTPS operation
- Test HTTP/HTTPS proxy operation
- Check reading and updating of all fields
Stress testing (HIGH)
- - Searching for long lists - Bad input data
Character sets: test with Umlauts (HIGH)
- - Test Umlauts in UTF-8 set to server - Test Umlauts in ISO-8859-1 set from server
- Compatibility testing
Refactoring (MEDIUM/LOW)
- Message catalog
- TODO's in code
Internal Documentation (LOW)
- Convert notes/DesignNotes into Wiki
- Revision sequence
- Named ranges
- URLS for REST transactions
- XML structures
- - Returned records - Insert/update records
User Documentation (LOW)
- To do in Wiki