This commit is contained in:
@@ -31,6 +31,13 @@ June 1st
|
||||
|
||||
MISC ITEMS THAT CAME UP
|
||||
|
||||
## V8Migrate
|
||||
todo: notification subscriptions need to come across first so that subsequent notifications will process
|
||||
e.g. when a contracted client with a current contract is imported it needs to also set the notification for it
|
||||
todo: custom fields field names are not coming across, still show "Custom 1" when shoudl show whatever is set
|
||||
todo: assigned doc not found text has too many newlines in it, should just sit on one line in exported notes
|
||||
todo: dirty big test again with contracts etc
|
||||
|
||||
## CLIENT MISC ITEMS
|
||||
|
||||
todo: BUGBUG delete all tags from customer, go back in and zone2 appears for some reason
|
||||
@@ -94,6 +101,17 @@ todo: WHEN HAVE WORKORDER FORM customer alert notes
|
||||
|
||||
## SERVER MISC ITEMS
|
||||
|
||||
todo: NOTIFICATION after the fact
|
||||
what happens when a user subscribes to a notification after an object was created
|
||||
for example if a unit has a contract and they subscribe to contract expiring they won't get notified about units unless they are edited and saved
|
||||
*after* the user subscribed
|
||||
What did v7 do?
|
||||
How to handle this??
|
||||
Ideally it would work with existing objects and not require them all to be edited or is that an issue, can it be good enough that it works going forward?
|
||||
Most subscriptions won't matter as they are direct immediate and one off but the timed and aged ones are definitely an issue.
|
||||
It might have to run through those and subscribe in the user, maybe a static op on a *Biz object that you call and say "subscribe this user to all subs" and it iterates
|
||||
the biz objects one by one and sets as appropriate??
|
||||
|
||||
todo: ContractExpiring event needs to be added to notification processor for Unit, Customer and HeadOffice
|
||||
todo: every biz rule should have as much as possible a corresponding db check constraint to ensure people don't import bad data directly or do direct edits and break shit
|
||||
e.g. contractable objects should mirror check for expiry date and not null, so basically both can be null or both not null but no other combo is valid
|
||||
@@ -197,12 +215,11 @@ todo: Changes to allow in place updates of server without erasing data:
|
||||
|
||||
|
||||
|
||||
CURRENTLY DOING: Contract server loose ends
|
||||
|
||||
todo: v8migrate
|
||||
todo: post for testing
|
||||
|
||||
CURRENTLY DOING: working up to workorder which has to be done in next 3 weeks. Look into it and will likely spot things that need to be done before it that I missed
|
||||
|
||||
todo b4 starting workorder list:
|
||||
WorkorderStatus (check cases, very many supposedly, but they are likely more about the workorder and notification than about the status itself)
|
||||
|
||||
|
||||
------------------------------------------
|
||||
|
||||
@@ -251,9 +268,6 @@ EACH OBJECT DEV CYCLE:
|
||||
## OBJECT ORDER
|
||||
Preliminary order to get the ball rolling, these are the easiest starting point:
|
||||
|
||||
Contract
|
||||
big one, tons of cases, will likely be implemented then need tweaking until it's right but the cases are all gold Jerry, gold!
|
||||
|
||||
Inventory Migration
|
||||
migrate inventory added to v8migrate as final step of export; code it based on balances and also insert serials etc
|
||||
it checks the balances in v8 then compares to v7 then issues an adjustment to bring into sync
|
||||
@@ -325,14 +339,14 @@ aclientservicerequest
|
||||
DEPRECATED - acontact -
|
||||
acontacttitle
|
||||
|
||||
acontract
|
||||
Xacontract
|
||||
aregion - TAG
|
||||
|
||||
acontractrate
|
||||
Xacontractrate
|
||||
acontract
|
||||
arate
|
||||
|
||||
adispatchzone - TAG
|
||||
X adispatchzone - TAG
|
||||
aregion - TAG
|
||||
|
||||
DEPRECATED / HANDLED AUTOMATICALLY BY IMPORT afile
|
||||
|
||||
Reference in New Issue
Block a user