This commit is contained in:
@@ -406,21 +406,17 @@ Coded, tested, done:
|
||||
OutsideServiceReceived
|
||||
OutsideServiceOverdue
|
||||
CustomerServiceImminent
|
||||
WorkorderTotalExceedsThreshold
|
||||
|
||||
|
||||
todo 3: workorder notifications to code and test:
|
||||
|
||||
Note found in source code from earlier possible implications:
|
||||
//THESE TWO ARE REDUNDANT:
|
||||
this is actually workorderstatuschange because can just pick any status under workorderstatuschange to be notified about
|
||||
WorkorderCompleted = 30, //*travel work order is set to any status that is flagged as a "Completed" type of status. Customer & User
|
||||
//This one could be accomplished with WorkorderStatusAge, just pick a Completed status and set a time frame and wala!
|
||||
WorkorderCompletedFollowUp = 32, //* travel workorder closed status follow up again after this many TIMESPAN
|
||||
|
||||
WorkorderTotalExceedsThreshold = 23,//* "the Andy" Workorder updated / created, based on balance total so conditional on DecValue
|
||||
WorkorderCreatedForCustomer = 31, //*Service work order is created for Customer, only applies to that customer user notify sub for that customer, customer id is in conditional ID value for subscription
|
||||
WorkorderCompletedFollowUp = 32, //* Service workorder closed status follow up again after this many TIMESPAN
|
||||
is this a thing? Should it be a thing??
|
||||
|
||||
|
||||
|
||||
|
||||
TODO: Hiding sections not used when empty and now added from the menu to present a cleaner empty work order
|
||||
|
||||
todo: notify event list table needs to show status of workorder (all fields) ideally
|
||||
|
||||
Reference in New Issue
Block a user