This commit is contained in:
@@ -208,7 +208,10 @@ todo: cypress testing for load testing etc
|
||||
|
||||
## SERVER MISC ITEMS
|
||||
|
||||
|
||||
todo: tag based notifications need to be rechecked if tags change, not just the field(s) in question for that notification
|
||||
for example, user makes a workorder with closeby date and tags but tags don't match when saves
|
||||
user realizes missed a critical tag, adds it and saves; notification should then check again if can apply whatever it was
|
||||
Use SameTags = NotifyEventHelper.TwoObjectsHaveSameTags(proposedObj.Tags, currentObj.Tags); to make it easy (workorder complete by)
|
||||
|
||||
todo: //TODO: Iterate all notification tagged items, use the one with the MOST matching tags
|
||||
see how contract labor done in workorder, idea is it iterate from the subscription with the most numerous amount of tags to least in order to ensure that the most specfic tag set is matched first
|
||||
@@ -367,9 +370,7 @@ todo: many biz objects are not using new PUT methodology
|
||||
CURRENTLY DOING: workorder round two electric boogaloo
|
||||
basics first then increasingly esoteric features
|
||||
|
||||
todo: tag based notifications need to be rechecked if tags change, not just the field(s) in question for that notification
|
||||
for example, user makes a workorder with closeby date and tags but tags don't match when saves
|
||||
user realizes missed a critical tag, adds it and saves; notification should then check again if can apply whatever it was
|
||||
|
||||
|
||||
todo 3: notification
|
||||
Go through all notification types and pick out relevant ones, paste here in a list then implement one by one and test each
|
||||
|
||||
Reference in New Issue
Block a user