This commit is contained in:
@@ -68,9 +68,9 @@ TODO: MAIN GRID LIST ANALYSIS, DESIGN AND COMPLETION KEEPING IN MIND TTM
|
||||
- Plugins: in v7 plugins could be enacted against individually selected from list of items or all etc
|
||||
- Maybe a good middle ground to allow for more flexibility with mass ops is to allow up to large but arbitrary number to prevent an *all* option, like 1000 or 5000 or something which should be enough for almost anything to be practically done in segments
|
||||
- i.e. report on all workorders for year maybe is too large but if filter by month then can print each month separately
|
||||
- CLIENT for selective ops only, for any feature that is going to commonly be required to use against *all* records it should be a defined route at the server and the server should handle it when client triggers
|
||||
|
||||
|
||||
- Reporting number of records will exactly follow grid display??
|
||||
- That was easy to grasp in v7...hmm...
|
||||
- CLIENT for selective ops only, for any feature that is going to commonly be required to use against *all* records it should be a defined route at the server and the server should handle it when client triggers (i.e. something like GDPR wiping of all client data etc)
|
||||
|
||||
- COLUMNS DISPLAYED
|
||||
- Crtical columns are the name or equivalent that is unique as the primary item
|
||||
|
||||
Reference in New Issue
Block a user