This commit is contained in:
@@ -7,11 +7,7 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
FIRST: Determine order to implement objects and write in below, try to list as thoroughly as possible by going over existing features and proposed new ones
|
NEXT UP: Customer
|
||||||
List should be objects in order of implementation, if new then flag with an asterisk * indicating it's a new feature that doesn't need import code
|
|
||||||
Lone wolf objects with the least dependencies (that are staying) to the most connected ones with the biggest graph (workorder, schedule ui) in that order
|
|
||||||
(If an object would normally be accessible via client ui from another object that won't be ported until later then can make up a set of links on a dashboard page
|
|
||||||
to use for temp testing purposes until can fully implement)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@@ -45,6 +41,11 @@ Preliminary order to get the ball rolling, these are the easiest starting point:
|
|||||||
|
|
||||||
|
|
||||||
Customer "Client"
|
Customer "Client"
|
||||||
|
Drop last service date column: case 3536
|
||||||
|
Import contacts as User's from v7, drop contact related fields: case 3356
|
||||||
|
Several UI related cases in rockfish for new Custom form, create user on fly and email creds, customer notes etc
|
||||||
|
|
||||||
|
|
||||||
HeadOffice
|
HeadOffice
|
||||||
Vendor
|
Vendor
|
||||||
case 3300 popup notes
|
case 3300 popup notes
|
||||||
|
|||||||
Reference in New Issue
Block a user