From 749a6440d2b19ae15c7759145ef3fcd1ce04f76d Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 28 Apr 2021 19:19:50 +0000 Subject: [PATCH] --- docs/8.0/ayanova/docs/svc-work-order-status.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/8.0/ayanova/docs/svc-work-order-status.md b/docs/8.0/ayanova/docs/svc-work-order-status.md index f3c315d5..deca38c1 100644 --- a/docs/8.0/ayanova/docs/svc-work-order-status.md +++ b/docs/8.0/ayanova/docs/svc-work-order-status.md @@ -6,4 +6,12 @@ todo: locking - locks workorder from edit (other than status for roles that are todo: completed - used for notification processing todo: select roles - who can select this status todo: remove roles - who can remove -todo: a section on why select and remove are there, how they can be used in conjunction with notifiation to enforce process control etc \ No newline at end of file + +todo: a section on why select and remove are there, how they can be used in conjunction with notifiation to enforce process control etc + +todo: A thorough section on PROCESS CONTROL with suggestions of commonly controlled aspects and hwo status satisifies them, e.g.: + Flow from intake to completion of final paper work + "New to be assessed and booked" - service manager / scheduler asses and assign to tech for repair + "Scheduled" - set to a tech to do the work + "Service completed" or "Awaiting parts" or "Awaiting customer approval" or whatever common scenarios + "Accounting step" - service complete, up to accounting to take, print and invoice customer etc they then set it to "Final / completed / closed" etc.