This commit is contained in:
@@ -186,10 +186,18 @@ todo: many biz objects are not using new PUT methodology
|
||||
|
||||
|
||||
|
||||
CURRENTLY DOING: LOOSE ENDS, my misc above and Joyce Misc list items below
|
||||
CURRENTLY DOING: workorder (status)
|
||||
|
||||
todo: workorder status first, it's a table of created items, keep properties from v7 but add the following properties:
|
||||
RolesAllowed - who can select the status (still shows if they can't select but that's the current status, like active does)
|
||||
EndPoint bool - this is a final status indicating all work on the workorder is completed, affects notification etc
|
||||
Do I need this? It was intended for notification but can notification be changed to just say if not status XXX by completion time then notify??
|
||||
that way don't need to particularly indicate any status does anything
|
||||
check if other cases require an endpoint "finished" status
|
||||
|
||||
|
||||
working up to workorder which has to be done in next 3 weeks. Look into it and will likely spot things that need to be done before it that I missed
|
||||
todo: updating, in bits seperately, entirely at once?
|
||||
concurrency issue reduction
|
||||
|
||||
todo b4 starting workorder list:
|
||||
WorkorderStatus (check cases, very many supposedly, but they are likely more about the workorder and notification than about the status itself)
|
||||
@@ -961,3 +969,4 @@ build 105
|
||||
Needs more thought I guess.
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user