This commit is contained in:
@@ -2,51 +2,40 @@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 6 - "REALITY" All in on porting over all the real objects from v7
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
“Accept the things to which fate binds you, and love the people with whom fate brings you together,but do so with all your heart.”
|
||||
|
||||
― Marcus Aurelius, Meditations
|
||||
|
||||
|
||||
## BIG PICTURE TO RELEASE
|
||||
|
||||
Big outstanding things by time:
|
||||
|
||||
Joyce needs early access as possible to quotes pm etc for reporting
|
||||
schedule has no new reporting implications or at least no regular ones
|
||||
migrate early and often also important as need a lot of testing and feedback early on this one, at least need to find huge stuff that alters design of wo etc
|
||||
|
||||
Misc blizzard of things that came up
|
||||
Schedule form
|
||||
Quote
|
||||
PM
|
||||
Reports
|
||||
Docs
|
||||
Add-ons
|
||||
Installer
|
||||
Rockfish / licensing good to go level
|
||||
|
||||
|
||||
## ROUGH SCHEDULE
|
||||
|
||||
July
|
||||
quote*, pm* implementations
|
||||
migrate
|
||||
Customer UI / CSR techs ui accept to wo etc
|
||||
Schedule form
|
||||
Blizzard DOUBLE STARRED #1 ITEMS ONLY
|
||||
|
||||
quote
|
||||
pm
|
||||
migrate workorders
|
||||
migrate quotes
|
||||
migrate pm
|
||||
Misc "blizzard"
|
||||
Customer UI
|
||||
CSR techs ui accept to wo etc
|
||||
Schedule form
|
||||
Review all v8 cases top to bottom and triage / implement
|
||||
V8Migrate completion
|
||||
All stock reports (and schedule ones)
|
||||
Aug
|
||||
Manual pages
|
||||
Installer
|
||||
Seeder / evaluation system worked out fully and implemented
|
||||
Manual pages docs
|
||||
Extensions to replace current add-on's (accounting etc)
|
||||
Load testing
|
||||
Beta testing
|
||||
Rockfish / Back end infrastructure
|
||||
Rockfish / Back end infrastructure (round robin license fetching / mirror license domains / machines)
|
||||
Biz decisions about pricing, licensing, hosting etc
|
||||
Sept 1st
|
||||
Release!
|
||||
|
||||
|
||||
## CURRENTLY WORKING ON: Workorder
|
||||
## CURRENTLY WORKING ON: blizzard **
|
||||
|
||||
|
||||
## MISC ITEMS THAT CAME UP
|
||||
@@ -73,6 +62,13 @@ TODO: Need stress test for client that can generate workorders in parallel for
|
||||
|
||||
## V8MIGRATE
|
||||
|
||||
|
||||
note: Inventory Migration (just a note I found, not sure if relevant)
|
||||
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
|
||||
this way (last thing) we are always covered no matter what happens with wo import etc
|
||||
|
||||
|
||||
todo:1 IMPORT workorders FROM V7 needs to be coded once the cases are completed so it can be tested thoroughly and ongoing
|
||||
note that v7 wostatus needs to be dual imported into both new wostate and new woitemstatus separately
|
||||
Joyce suggested making it optional to have the import-v7 tag
|
||||
@@ -119,7 +115,7 @@ todo:1 workorders - need to set billing and service address from customers on mi
|
||||
Custom fields - when set to Text takes up extra height. I understand that this is because of the "potential" text, i.e. that could have multiple rows etc. Is there ANY way to minimize these so only shows additional space IF actually used?
|
||||
[#will look into it, not sure what can be done, the layout is pretty rigidly fixed within the UI framework to be able to work properly without conflict with the layout, but maybe there's something#]
|
||||
|
||||
-1 case 3864 Joyce misc item - add more viz fields to po:
|
||||
-1** case 3864 Joyce misc item - add more viz fields to po:
|
||||
Sample data for a PO
|
||||
**VendorViz shows ONLY the vendor name:
|
||||
-where and how to get address, contact name, phone number(s) for the selected vendor?
|
||||
@@ -127,7 +123,7 @@ todo:1 workorders - need to set billing and service address from customers on mi
|
||||
**DropShipToCustomerViz shows ONLY the customer name:
|
||||
-how to get address, contact name(s), phone number(s) for the selected Ship to Customer?
|
||||
|
||||
todo:1 joyce requested fields to add to reports viz fields
|
||||
todo:1** joyce requested fields to add to reports viz fields
|
||||
PO - Customer address and contact information (for PO where a customer has been selected to be shipped to)
|
||||
|
||||
|
||||
@@ -167,7 +163,7 @@ todo:1 joyce requested fields to add to reports viz fields
|
||||
|
||||
|
||||
|
||||
bugbug:1 direct notification errors out
|
||||
bugbug:1** direct notification errors out
|
||||
user->direct notification
|
||||
|
||||
|
||||
@@ -191,7 +187,7 @@ todo:3 link back to list from single edit form
|
||||
narrow mode no shortcut because they could use the nav menu anyway and because fuck em, that's why :)
|
||||
|
||||
|
||||
todo:1 notifications new count seems to be double getting on each iteration
|
||||
todo:1** notifications new count seems to be double getting on each iteration
|
||||
|
||||
todo:3 Seeding UI keep track of timing and later down the road when firmed up, provide estimate (average server will take):
|
||||
2021-05-31 10:26:45.4801|INFO|Seeder|Small level sample data seeded in 27 seconds
|
||||
@@ -200,7 +196,7 @@ todo:3 Seeding UI keep track of timing and later down the road when firmed up, p
|
||||
2021-05-31 12:06:34.2680|INFO|Seeder|HUGE level sample data seeded in 24 minutes and 54 seconds
|
||||
|
||||
todo:2 need to track fetched keys vs used keys so can tell if fetched a key that I don't need or stopped using due to code change
|
||||
todo:1 need to track fetched keys that don't exists, should bomb immediately so I can remove them, they will eat up traffic for no useful purpose!!
|
||||
todo:2 need to track fetched keys that don't exists, should bomb immediately so I can remove them, they will eat up traffic for no useful purpose!!
|
||||
|
||||
todo:2 PO (workorder already done) strip all *viz fields from object before sending over the wire from client to server
|
||||
Setting their value to undefined stops them being sent so do that, but remember they then need to be updated on the return record
|
||||
@@ -231,7 +227,7 @@ todo:2 Contract override by TAGS
|
||||
todo:3 form field customization add a "reset" feature to reset to default for when people fuck it up
|
||||
basically just show all fields and remove the required from fields
|
||||
|
||||
todo:1 add NOW button to date picker just like time picker that does the same thing
|
||||
todo:1** add NOW button to date picker just like time picker that does the same thing
|
||||
|
||||
todo:2 Not in love with the "Error api2200" as the only error text in the box
|
||||
sometimes it has things you can't see in the form
|
||||
@@ -304,14 +300,14 @@ todo:2 confirm erase database should reset all id values if they aren't reset al
|
||||
|
||||
todo:2 use trans key "AlertNotes" in place of any popup notes variation
|
||||
|
||||
todo:1 poitem edit form currency fields when updated by server on save lose currency format and show as raw decimal number
|
||||
todo:2 poitem edit form currency fields when updated by server on save lose currency format and show as raw decimal number
|
||||
maybe currency control does not respond to underlying data changes it didn't initiate?
|
||||
seems maybe it's ok in main form but that's maybe just because it doesn't change values automatically
|
||||
|
||||
todo:3 datatable single select mode, is this even a thing?
|
||||
if not then I should remove that code, it's just taking up space and complicating shit for no reason
|
||||
|
||||
todo: Whats new in this release popup or link tied into the update process of the client??
|
||||
todo:3 Whats new in this release popup or link tied into the update process of the client??
|
||||
how about a link in the About page to the change long on our web server instead?
|
||||
|
||||
todo:2 it's a bit hard to click on a single digit or character link in a data table
|
||||
@@ -324,7 +320,7 @@ todo:2 remove widget now? Back and front (comment out obvs not remove entirely)
|
||||
|
||||
## SERVER MISC ITEMS
|
||||
|
||||
todo:1 Joyce was having trouble getting a license request email response from rockfish when trialing
|
||||
todo:1** Joyce was having trouble getting a license request email response from rockfish when trialing
|
||||
it appeared it was not sending the confirmation check email, double check what the fuck
|
||||
|
||||
|
||||
@@ -351,9 +347,8 @@ todo:1 tag based notifications need to be rechecked if tags change, not just the
|
||||
todo:1 //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
|
||||
|
||||
todo:1 custom required rules only apply to new records!!
|
||||
|
||||
todo:1 Contract Duplicate throws exception at server (id attempted to be set, probably forgot to set copy to null id)
|
||||
todo:1** Contract Duplicate throws exception at server (id attempted to be set, probably forgot to set copy to null id)
|
||||
probably not an issue anymore
|
||||
|
||||
todo:1 Reports need to generate under a file name that is informative (this applies to every object)
|
||||
@@ -382,7 +377,7 @@ todo:1 server boot log should show exact .net framework version in use, currentl
|
||||
NOW
|
||||
....
|
||||
|
||||
todo:1 Error at the devops server just looking at gold contract:
|
||||
todo:1** Error at the devops server just looking at gold contract:
|
||||
|
||||
2021-03-26 18:21:36.8769|ERROR|SERVER|Error=>System.NullReferenceException: Object reference not set to an instance of an object.
|
||||
at AyaNova.Biz.ContractBiz.PopulateVizFields(Contract o, List`1 contractOverrideTypeEnumList, Dictionary`2 preTrans) in C:\data\code\raven\server\AyaNova\biz\ContractBiz.cs:line 531
|
||||
@@ -530,14 +525,13 @@ todo:2 many biz objects are not using new PUT methodology
|
||||
########################################################################################################################
|
||||
|
||||
|
||||
CURRENTLY DOING:
|
||||
|
||||
AFTER ABOVE ITEMS AND HAVE SUBSTANTIALLY COMPLETED WO
|
||||
CURRENTLY DOING: **1 blizzard items, then a release for Friday then quote etc see top above
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
------------------------------------------
|
||||
|
||||
|
||||
|
||||
@@ -580,32 +574,7 @@ EACH OBJECT DEV CYCLE:
|
||||
imports and flows through to new front end viewable and searchable and printable etc
|
||||
|
||||
|
||||
|
||||
## OBJECT ORDER
|
||||
Preliminary order to get the ball rolling, these are the easiest starting point:
|
||||
|
||||
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
|
||||
this way (last thing) we are always covered no matter what happens with wo import etc
|
||||
|
||||
|
||||
|
||||
|
||||
Workorder
|
||||
When do this need to go back and do a bunch of //MIGRATE_OUTSTANDING
|
||||
i.e. show all
|
||||
todo: Consider adding latitude / longitude to wo, quote, pm objects
|
||||
rate split
|
||||
can copy over from the unit or customer or set themselves
|
||||
and can always hide
|
||||
means wo could be scheduled for ad-hoc locations and serviced that way, i.e. a truck parked on the side of the highway etc
|
||||
|
||||
Quote
|
||||
|
||||
PM
|
||||
|
||||
Schedule form
|
||||
|
||||
|
||||
|
||||
@@ -623,309 +592,6 @@ Preliminary order to get the ball rolling, these are the easiest starting point:
|
||||
- VendorType ## LATE ADDITION
|
||||
|
||||
|
||||
## v7 DB DEPENDENCIES
|
||||
object
|
||||
depends on
|
||||
|
||||
AssignedDoc * Already handled automatically by v8 migrate
|
||||
none
|
||||
|
||||
xaclient
|
||||
adispatchzone - TAG
|
||||
aheadoffice
|
||||
aworkorder
|
||||
|
||||
xaclientgroup - TAG
|
||||
none
|
||||
|
||||
xaclientnote
|
||||
aclientnotetype - TAG
|
||||
aclient
|
||||
|
||||
xaclientnotetype - TAG
|
||||
none
|
||||
|
||||
DEPRECATED - aclientnotifyevent -
|
||||
none
|
||||
|
||||
aclientservicerequest
|
||||
aworkorderitem
|
||||
|
||||
DEPRECATED - acontact -
|
||||
acontacttitle
|
||||
|
||||
Xacontract
|
||||
aregion - TAG
|
||||
|
||||
Xacontractrate
|
||||
acontract
|
||||
arate
|
||||
|
||||
X adispatchzone - TAG
|
||||
aregion - TAG
|
||||
|
||||
DEPRECATED / HANDLED AUTOMATICALLY BY IMPORT afile
|
||||
none
|
||||
|
||||
xaglobal
|
||||
ataxcode
|
||||
aworkorder
|
||||
aworkorderstatus
|
||||
|
||||
xaglobalex
|
||||
none
|
||||
|
||||
xaheadoffice
|
||||
aclientgroup - tag
|
||||
acontract
|
||||
|
||||
aintegration
|
||||
none
|
||||
|
||||
aintegrationmap
|
||||
aintegration
|
||||
|
||||
Xaloanitem
|
||||
aregion - TAG
|
||||
aworkorderitemloan
|
||||
|
||||
xamemo
|
||||
auser
|
||||
|
||||
DEPRECATED - anotify*
|
||||
lots of tables, but it's all obsolete and won't be ported
|
||||
|
||||
HANDLED BY IMPORT - aobjectcustomfield
|
||||
(defines custom fields, is part of base import already, nothing special required here)
|
||||
|
||||
apart
|
||||
apartassembly
|
||||
apartcategory - TAG
|
||||
aunitofmeasure
|
||||
avendor
|
||||
|
||||
apartassembly
|
||||
none
|
||||
|
||||
apartbywarehouseinventory
|
||||
apart
|
||||
apartwarehouse
|
||||
|
||||
apartcategory - TAG
|
||||
none
|
||||
|
||||
apartinventoryadjustment
|
||||
none
|
||||
|
||||
apartinventoryadjustmentitem
|
||||
apart
|
||||
apartinventoryadjustment
|
||||
apartwarehouse
|
||||
|
||||
apartserial
|
||||
apartinventoryadjustmentitem
|
||||
apurchaseorderreceiptitem
|
||||
aworkorderitempart
|
||||
|
||||
apartwarehouse
|
||||
aregion - TAG
|
||||
|
||||
xapriority
|
||||
none
|
||||
|
||||
xaproject
|
||||
aregion - TAG
|
||||
auser
|
||||
|
||||
apurchaseorder
|
||||
aproject
|
||||
avendor
|
||||
|
||||
apurchaseorderitem
|
||||
apart
|
||||
apartwarehouse
|
||||
apurchaseorder
|
||||
ataxcode
|
||||
aworkorderitempartrequest
|
||||
|
||||
apurchaseorderreceipt
|
||||
avendor
|
||||
|
||||
apurchaseorderreceiptitem
|
||||
apart
|
||||
apurchaseorder
|
||||
apurchaseorderitem
|
||||
apurchaseorderreceipt
|
||||
|
||||
xarate
|
||||
aclientgroup - tag
|
||||
arateunitchargedescription - DEPRECATED per case 3432
|
||||
aregion - TAG
|
||||
|
||||
DEPRECATED case 3432 - arateunitchargedescription
|
||||
none
|
||||
|
||||
xaregion - TAG
|
||||
aworkorderstatus ?! WTF?
|
||||
|
||||
xregionnotifystat ?wtf is this?
|
||||
aregion - TAG
|
||||
|
||||
REPLACED NEW FORMAT - areport
|
||||
aregion - TAG
|
||||
|
||||
xaScheduleableUserGroup - TAG
|
||||
none
|
||||
|
||||
xascheduleableusergroupuser
|
||||
aScheduleableUserGroup - TAG
|
||||
auser
|
||||
|
||||
aschedulemarker (now "Reminder")
|
||||
none ?must be at least user in there...weird
|
||||
|
||||
DEPRECATED - asecuritygroup (nope)
|
||||
none
|
||||
|
||||
xaservicebank
|
||||
none
|
||||
|
||||
atask
|
||||
none
|
||||
|
||||
ataskgroup
|
||||
none
|
||||
|
||||
ataskgrouptask
|
||||
atask
|
||||
ataskgroup
|
||||
|
||||
xataxcode
|
||||
none
|
||||
|
||||
aui* (these are all v7 UI saved settings that are not applicable to v8)
|
||||
|
||||
xaunit
|
||||
aclient
|
||||
aunitmodel
|
||||
|
||||
xaunitmeterreading
|
||||
aworkorderitem
|
||||
|
||||
xaunitmodel
|
||||
aunitmodelcategory - TAG
|
||||
avendor
|
||||
|
||||
xaunitmodelcategory - TAG
|
||||
none
|
||||
|
||||
DEPRECATED NO MORE - aunitofmeasure
|
||||
none
|
||||
|
||||
xaunitservicetype - TAG
|
||||
none
|
||||
|
||||
xauser
|
||||
adispatchzone - TAG
|
||||
aheadoffice
|
||||
apartwarehouse
|
||||
asecuritygroup
|
||||
avendor
|
||||
aworkorder
|
||||
|
||||
xausercertifcation* (these are now tags and already rolled into v8 migrate tool)
|
||||
|
||||
xausermru DEPRECATED
|
||||
xauserright DEPRECATED
|
||||
|
||||
xauserskill* (now tags and already accounted for in v8 migrate)
|
||||
|
||||
xavendor
|
||||
none
|
||||
|
||||
xawikipage* (already accounted for in v8 migrate code, object by object will export)
|
||||
|
||||
aworkorder (new structure, some of these are no longer joined due to seperation of wo types in v8)
|
||||
aproject
|
||||
aregion - TAG
|
||||
aworkordercategory - TAG
|
||||
aworkorderpreventivemaintenance
|
||||
aworkorderquote
|
||||
|
||||
xaworkordercategory - TAG
|
||||
none
|
||||
|
||||
aworkorderitem
|
||||
apriority
|
||||
aunit
|
||||
aunitservicetype - TAG
|
||||
aworkorderitemtype - TAG
|
||||
aworkorderstatus
|
||||
|
||||
aworkorderitemlabor
|
||||
arate
|
||||
aservicebank
|
||||
ataxcode
|
||||
aworkorderitem
|
||||
|
||||
aworkorderitemloan
|
||||
aloanitem
|
||||
ataxcode
|
||||
aworkorderitem
|
||||
|
||||
aworkorderitemmiscexpense
|
||||
ataxcode
|
||||
aworkorderitem
|
||||
|
||||
aworkorderitemoutsideservice
|
||||
avendor
|
||||
aworkorderitem
|
||||
|
||||
aworkorderitempart
|
||||
apart
|
||||
apartserial
|
||||
apartwarehouse
|
||||
ataxcode
|
||||
aworkorderitem
|
||||
|
||||
aworkorderitempartrequest
|
||||
apart
|
||||
apartwarehouse
|
||||
apurchaseorderitem
|
||||
aworkorderitem
|
||||
|
||||
aworkorderitemscheduleduser
|
||||
arate
|
||||
aworkorderitem
|
||||
|
||||
aworkorderitemtask
|
||||
atask
|
||||
ataskgroup
|
||||
aworkorderitem
|
||||
|
||||
aworkorderitemtravel
|
||||
arate
|
||||
aservicebank
|
||||
ataxcode
|
||||
aworkorderitem
|
||||
|
||||
xaworkorderitemtype - TAG
|
||||
none
|
||||
|
||||
aworkorderpreventivemaintenance
|
||||
aworkorder
|
||||
aworkorderstatus
|
||||
|
||||
aworkorderquote
|
||||
aworkorder
|
||||
|
||||
aworkorderservice
|
||||
aworkorderpreventivemaintenance
|
||||
aworkorderstatus
|
||||
|
||||
xaworkorderstatus
|
||||
none
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -940,7 +606,6 @@ todo: CYPRESS TEST DATE / TIME / DATE_TIME controls switched back to vuetify one
|
||||
https://github.com/vuetifyjs/vuetify/issues/10988#issuecomment-726089949
|
||||
|
||||
|
||||
|
||||
todo: Schedule form
|
||||
- This one is big but requires the data to be there so as soon as implement enough things that are scheduleable then do this
|
||||
- printing / reporting schedule? Do-able?
|
||||
|
||||
Reference in New Issue
Block a user