From ee995d66795afd2fb2d8004f2467329df6045d85 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 7 Jul 2021 15:53:40 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 27 +++++++++++---------------- 1 file changed, 11 insertions(+), 16 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index e3103d6c..95fb081e 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -421,19 +421,7 @@ todo: many biz objects are not using new PUT methodology CURRENTLY DOING: - woitem selected: - copy to wo - $ayiCopy - ""CopyToWorkOrder"" translation key - allow to copy to any non locked workorder - can filter by customer and defaults to current customer - also presents current wo for when user wants to duplicate the woitem to the same wo - allow user to punch in wo# for copy to feature rather than a list selection?? - may be risky, they copy then don't know which one they copied to by accident. - "Move" not required due to user being able to just delete a woitem on the source effectively replicating a move?? - or is move a common use-case for this? -bugbug?: duplicate going to same workroder item id not cleared?? TODO 2 (all 2's): V7 features on wo I haven't coded yet @@ -1249,11 +1237,18 @@ MID CENTURY MODERN TUNES - https://www.allmusic.com/album/ultra-lounge-vol-14-bo BUILD CHANGES OF NOTE -BUILD 113 +BUILD 114 + +- Copy work order item implemented to recreate functionality of v7 + Can now Copy woitem to *any* work order + Completely new functionality not in v7 + Can also copy to the *same* workorder which is handy to duplicate a bunch of woitems that are the same + Copied item is inserted into target work order as if user had just entered it + i.e. all done at client end and not saved automatically. + This means user can edit as necessary before first save and avoids a bunch of fuckery + Note: v7 "move" woitem feature is intentionally not implemented + user can replicate by copy and then delete source woitem -- WorkorderItemUnits "Add multiple Units" feature implemented. Accessible from context menu in woitemunits list header in workorder - This is a good "sneak peek" feature, particularly Scott at 4alarm would be *very* interested to see this -- Fixed regression with workorderitem descendant report data include all children where it was not populating the woitem properly