This commit is contained in:
2021-03-25 16:47:18 +00:00
parent c1b5015df4
commit 5ba2173a4d

View File

@@ -198,25 +198,6 @@ todo: workorder Status table joined to Workorder
Has fields for statusid, workorderid, timestamp, userid Has fields for statusid, workorderid, timestamp, userid
Write only, always just adds to the table Write only, always just adds to the table
todo: workorder notifications remove #30 and #32 as redundant
WorkorderStatusChange = 4,//* Workorder object, any *change* of status including from no status (new) to a specific conditional status ID value
WorkorderStatusAge = 24,//* Workorder object Created / Updated, conditional on exact status selected IdValue, Tags conditional, advance notice can be set
//THESE TWO ARE REDUNDANT:
this is actually workorderstatuschange because can just pick any status under workorderstatuschange to be notified about
WorkorderFinished = 30, //*Service work order is set to any status that is flagged as a "Finished" type of status. Customer & User
//This one could be accomplished with WorkorderStatusAge, just pick a finished status and set a time frame and wala!
WorkorderFinishedFollowUp = 32, //* Service workorder closed status follow up again after this many TIMESPAN
todo: CHANGE WorkorderFinishStatusOverdue = 15,//* Workorder object not set to a "Finished" flagged workorder status type in selected time span from creation of workorder
Change this to a new type that is based on so many days *without* being set to a particular status
but first check if tied to contract response time stuff, how that's handled
that's closeby date in v7 but isn't that deprecated now without a "close"?
maybe I do need the Finished status bool thing above
todo: workorder global setting of which roles can change a workorder status?? todo: workorder global setting of which roles can change a workorder status??
in place of making certain status role specific? (above) in place of making certain status role specific? (above)