diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 7229794f..1be1bd36 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -506,12 +506,16 @@ todo:2 many biz objects are not using new PUT methodology CURRENTLY DOING: PM stuff: - generate & threshold intervals "hours, days, months, years" are the options with whole int values - seeder (all not active or else it will be a clusterfuck or maybe long time frames) + pmdatalist + front end report fields coming over properly - back end biz job to do generation + back end biz job to actually do the generation Clean up notification for PM's and Quotes as they are filled with service wo shit + Pore over quote and PM and look for workorder remnants, particularly biz actions and rules + Add back end rules as necessary for quotes and PM's + Sanity checks for PM settings will be a must here + Child->grandchild data lists for quotes and pm's like workorders release profit$ @@ -529,9 +533,22 @@ CURRENTLY DOING: PM stuff: "GenerateBefore":"Generate beforehand", "RepeatInterval": "Repeat interval" + /* + + "stopgeneratingdate TIMESTAMP, nextservicedate TIMESTAMP NOT NULL, generatedate TIMESTAMP, excludedaysofweek BOOL ARRAY NOT NULL, active BOOL NOT NULL, " + + "repeatunit INTEGER NOT NULL, generatebeforeunit INTEGER NOT NULL, repeatinterval INTEGER NOT NULL, generatebeforeinterval INTEGER NOT NULL, " + * public DateTime NextServiceDate { get; set; } + public PMTimeUnit RepeatUnit { get; set; } + public PMTimeUnit GenerateBeforeUnit { get; set; } + public int RepeatInterval { get; set; } + public int GenerateBeforeInterval { get; set; } + * public DateTime? GenerateDate { get; set; }//Internal, not exposed to UI and is the date to do the next generate on that takes into account generatebefore and next service date and is calcd when first created and after that when generate happens for next time see pmbiz top with reference v7 code + + */ + + PM TODO: case 3349 implement all possible grandchild collections in PM (same as quote)