This commit is contained in:
2021-06-16 21:48:58 +00:00
parent eb0a09b084
commit e144a8fbab
2 changed files with 11 additions and 29 deletions

View File

@@ -383,34 +383,13 @@ todo: many biz objects are not using new PUT methodology
CURRENTLY DOING: Work order notifications CURRENTLY DOING:
Steps to test notifications:
plain in app delivery
email delivery
non matching tag doesn't trigger delivery
matching tag triggers in app / email delivery
Coded, tested, done:
WorkorderCompletedStatusOverdue
WorkorderStatusChange
WorkorderStatusAge
ScheduledOnWorkorder
ScheduledOnWorkorderImminent
OutsideServiceReceived
OutsideServiceOverdue
CustomerServiceImminent
WorkorderTotalExceedsThreshold
WorkorderCompleted
todo 3: workorder notifications to code and test: todo 3: workorder notifications to code and test:
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 todo test this
This is a v7 feature and needs to be replicated
@@ -1290,19 +1269,22 @@ build 110
- workorder based notifications implemented - workorder based notifications implemented
WorkorderCompletedStatusOverdue WorkorderCompletedStatusOverdue
CustomerServiceImminent (customer user feature)
WorkorderStatusChange WorkorderStatusChange
WorkorderStatusAge WorkorderStatusAge
OutsideServiceOverdue
OutsideServiceReceived
ScheduledOnWorkorder ScheduledOnWorkorder
ScheduledOnWorkorderImminent ScheduledOnWorkorderImminent
WorkorderCompletedStatusOverdue OutsideServiceReceived
OutsideServiceOverdue
CustomerServiceImminent
WorkorderTotalExceedsThreshold
WorkorderCompleted (customer and inside user notification, properly works with headoffice type users and their customers)
WorkorderCreatedForCustomer (customer notification, properly works with headoffice type users and their customers)
- standard object CRUD notifications implemented for all workorder tree objects - standard object CRUD notifications implemented for all workorder tree objects
(note that child items in workorder tree that don't have their own tags [all but items and workorder item units] will use the work order header tags for determining notification) (note that child items in workorder tree that don't have their own tags [all but items and workorder item units] will use the work order header tags for determining notification)
- Administration -> Global settings form added all Customer "contact" login account related control settings - Administration -> Global settings form added all Customer "contact" login account related control settings
also implemented at UI so those settings will now affect what Customer or HeadOffice user sees when they login or attempt to subscribe to a notification
- Removed all visible references to Service Bank feature from all forms and front and back end - Removed all visible references to Service Bank feature from all forms and front and back end

View File

@@ -780,7 +780,7 @@ async function populateSelectionLists(vm) {
return window.$gz.store.state.customerRights.notifyCSRRejected; return window.$gz.store.state.customerRights.notifyCSRRejected;
case 21: case 21:
return window.$gz.store.state.customerRights.notifyServiceImminent; return window.$gz.store.state.customerRights.notifyServiceImminent;
case 30: case 30: //cust or inside user both
return window.$gz.store.state.customerRights.notifyWOCompleted; return window.$gz.store.state.customerRights.notifyWOCompleted;
case 31: case 31:
return window.$gz.store.state.customerRights.notifyWOCreated; return window.$gz.store.state.customerRights.notifyWOCreated;