admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-05-12 18:30:02 +00:00
parent 2d3117a891
commit 59908a8c40
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
ayanova/devdocs/todo.txt
View File

@@ -307,6 +307,14 @@ todo: many biz objects are not using new PUT methodology
CURRENTLY DOING: labors CURRENTLY DOING: labors
todo: taxes, line totals etc todo: taxes, line totals etc
todo: contract in effect at server to set discounts 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 ORDER: Travel, tasks, parts, loans, units, outside service