diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 9254ba63..892cd6b5 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -507,17 +507,23 @@ todo:2 many biz objects are not using new PUT methodology ######################################################################################################################## -CURRENTLY DOING: PM stuff: +CURRENTLY DOING: PM stuff biz rules / sanity checks + - 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 - GenerateBeforeInterval must be less than repeatinterval - exclude days of week can't be *all* days of the week + Add biz rule that a repeat interval can be no shorter than.... some value that is an absolute and calculated using date method and then total minutes or hours ro whatever + this allows users to enter a huge number of minutes and be allowed for example, all it cares about is how short, i.e. shortest allowed repeat interval + in v7 it was one hour which, if things go wrong is nice because it will mean only a max of 24 wo generated per day until they catch it + expose source PM in workorder data list so that can filter by that PM number and then mass delete if fucked up the generator + OR EQUIVALENT, there *MUST* be a way to mass delete a PM gone wrong resulting in many wo Non copyable fields should not surface in PM?? Like scheduser dates and loan dates and etc comment out, don't delete, might be useful later + Need event log for generation and unique event so users can quickly see what the fuck is happenign without resorting to the server log + Clean up notification for PM's and Quotes as they are filled with service wo shit + Add NEW notifications related to errors and stop generating below + Pore over quote and PM and look for workorder remnants, particularly biz actions and rules Error on generation should send a OPS notification? Or perhaps a notification to the service manager or ...?? maybe someone subscribes to PM generation error notification??