From 59908a8c40721e5e72519c6280da3caaa85f42ed Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 12 May 2021 18:30:02 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 8f276b7f..eb84f21f 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -307,6 +307,14 @@ todo: many biz objects are not using new PUT methodology CURRENTLY DOING: labors todo: taxes, line totals etc todo: contract in effect at server to set discounts etc + This is a bit of an issue due to contract id changes along with grandchild item changes stepping on each other. + What if the workorder saved top down when new but header last when not new?? + This way the pricing would get set on the final save + Would need to have a system to indicate a total refresh was necessary to reflect all pricing properly after contract applied + plus other things might need that as well, maybe if a full workorder is returned on save then it uses it otherwise just the + concurrency token is updated?? + + ORDER: Travel, tasks, parts, loans, units, outside service