From 5352b2f4d4bd00af273a9654b7ed56cea68b6cb9 Mon Sep 17 00:00:00 2001
From: John Cardinal <support@ayanova.com>
Date: Fri, 17 Jul 2020 21:25:54 +0000
Subject: [PATCH]

---
 ayanova/devdocs/todo.txt | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 4d3b6e90..f1c9cd63 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -16,6 +16,11 @@ ____________
 ## CURRENT STAGE: 
 	All Notify events are fleshed out in comments or coded in eventprocessor
 	determine next step... backup notify, ops notify fill in those todo's?
+todo: make widget biz object process events as template for replicating everywhere in all corebiz objects
+todo: subscribe to widget CRUD events
+todo: get delivery of widget CRUD events
+todo: ops and backup notify add code
+todo: ops and backup subscribe and confirm delivery and proper handling
 
 
 todo: //Open question - do we need a priority level for notifications, i.e. if system is having backup issue slightly more important than something run of the mill?