From 4d77a62f7877777497b7c0c30de25e6ef9627542 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Mon, 24 May 2021 20:04:32 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 7 +- .../src/components/work-order-item-tasks.vue | 744 ++++++++++++++++++ 2 files changed, 748 insertions(+), 3 deletions(-) create mode 100644 ayanova/src/components/work-order-item-tasks.vue diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 60d36f01..ee558265 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -342,9 +342,8 @@ todo: many biz objects are not using new PUT methodology -CURRENTLY DOING: WorkOrderItemTravel - -ORDER: Travel, tasks, parts, loans, units, outside service +CURRENTLY DOING: +ORDER: tasks, parts, loans, units, outside service todo: WorkorderItemPart- part prices are going to change / volatile so snapshot them (cost/charge) rates and taxes are ok to not snapshot, their values are protected once used but parts are volatile and should be snapshotted @@ -376,6 +375,8 @@ todo: is it really feasible to duplicate a workorder? What about all the side e todo: should be able to create a new workorder for a customer from that customers menu (same with other objects that have an identifiable customer) this was in v7 (from main grid not inside object but can't replicate that so this instead) +todo: r4eporting - need to add pre-caching code and populate *Viz throughout graph to workorder before testing printing code. + OVERALL - then full in front end and flow out to back end as required, remove any backend that was a defunct evolutionary path so no cruft left around diff --git a/ayanova/src/components/work-order-item-tasks.vue b/ayanova/src/components/work-order-item-tasks.vue new file mode 100644 index 00000000..a74a99f9 --- /dev/null +++ b/ayanova/src/components/work-order-item-tasks.vue @@ -0,0 +1,744 @@ + +