This commit is contained in:
2020-05-01 17:44:51 +00:00
parent 55cb756d89
commit 01cbe8b65b

View File

@@ -66,15 +66,33 @@ CURRENT TODOs
@@@@@@@@@@@ ROADMAP STAGE 2: @@@@@@@@@@@ ROADMAP STAGE 2:
STUBBING BIZ OBJECT STUBBING
todo:
go through all objects below in cases to see if they will be renamed or dropped or etc so don't create pointless objects
Consider making one of each of *all* Corebiz root object types but start with these ones first
todo: Make these objects in RAVEN:
Basic class:
public long Id { get; set; }
public uint ConcurrencyToken { get; set; }
[Required]
public string Name { get; set; }
public bool? Active { get; set; }
public string Notes { get; set; }
public string Wiki {get;set;}
public string CustomFields { get; set; }
public List<string> Tags { get; set; }
todo: stub primitive workorder and client at server (all attachable objs?) so can test export with big data now?
- just name and id and wiki?
pros: nice to have a framework in place to then have the scope to work with
cons: won't be real so will need to be updated drastically as time goes by
Start with a simple biz/controller/db object predefined to make copies from by stripping widget back?
Need types defined as well and maybe LT?
TYPES: Would be corebiz, wikiable, attachable, custom fields, tags, searchable etc
WORKORDER CHANGES WORKORDER CHANGES
Raven to have separate objects for each workorder type, and seperate db tables etc Raven to have separate objects for each workorder type, and seperate db tables etc