This commit is contained in:
2022-06-15 01:16:42 +00:00
parent c10ff14a87
commit eb9175153d
9 changed files with 289 additions and 8 deletions

View File

@@ -1,6 +1,13 @@
# now
DOING: adding integration objects and routes for qbi and others
todo: document this in the developer section
todo: needs a front end to show the integration log, the integrations as a collection list and openable item where it can be disabled, deleted etc
needs to be available to bizadmin I guess and possibly accounting?? or should each integration control which roles see it??
or should the UI for each integration be *in* the integration itself and also in one place for biz admin to super control all integrations and troubleshoot log sb available to ops
todo: doc front end additions for integrations
JUST DONE: posted rc.1 updated forum (and turned off "views" column in custom css in forum as well it was looking pathetic)
@@ -17,7 +24,8 @@ todo: BIG PICTURE
QBI NEEDS TO BE DONE BEFORE RAVEN RELEASE AS RAVEN MAY REQUIRE MORE OBJECTS FOR DATA MAPPING AND OPTIONS SAVING IN CENTRAL LOCATION ETC
This saves users needing to back up their local QBI only settings and mappings separate from RAVEN backup
Integration objects and integration log plus front end to see that shit and remove / control it
QBI order of release decision (does raven qbi need to be released along with v8 simultaneously??)
if yes then need to whip that shit up pronto with a beta to go with RC for raven
figure out how many active qbi users, like will this prevent most people from upgrading?