admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2020-05-03 19:58:10 +00:00
parent 9fd724be60
commit f566ad882a
1 changed files with 23 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
ayanova/devdocs/todo.txt
View File

@@ -69,15 +69,12 @@ CURRENT TODOs
@@@@@@@@@@@ ROADMAP STAGE 2:
BIZ OBJECT STUBBING FOR EXPORT TESTING OF HUGE ATTACHMENTS AND WIKI AND ATTACHED DOCS
CURRENT ITEM:
BIZ OBJECT STUBBING FOR EXPORT TESTING OF HUGE ATTACHMENTS AND WIKI AND ATTACHED DOCS
Modify v8 export to have an intermediate form where user chooses options
Add option to export assigned docs as attachments
Add method to handle this and gracefully accept missing docs as that will be quite common (log them I guess)
Modify v8 export to export everything (at least teh wikiable and attachable and custom fieldable)
Uniquify: go through all and check which ones need to be uniquified by checking db schema of v7 or biz rules maybe
Uniquify NAMES: go through all and check which ones need to be uniquified by checking db schema of v7 or biz rules maybe
this is a v8 export plugin concern, not a RAVEN server concern
MIGRATE these deprecated things off of a USER object created just to host their stuff (user because only biz admin has full rights to user)
Put them in an INACTIVE, NO RIGHTS User with the following
@@ -99,15 +96,9 @@ todo: PLANNING workorder data and class and route structure:
likely follows biz object decision
Use foreign keys!!
Consider UI in this as well, will need to decide at least what is visible when
All workorder in one document and just really really tall? (people bitch about RI requiring too many navigation steps to get to shit)
Header and items in one document then bottom in seperate pages?
Is it going to be far easier to code this bitch if I have all the workorder data at hand or..?
How does WBI handle all this because it's kind of the poster child for RAVEN
Workorder is one of those things that may require different views for phone and tablet and laptop etc
Kind of like two views, tiny phone and anything larger
On a PC people will want and expect it to look as much like v7 workorder as possible, maybe that's still a valid layout
just tweaked to work better as a web app a bit but theoretically I could almost duplicate that layout with the tools I have
TTM!! Don't re-invent the wheel!
PLANNING Workorder templates
Keep as is or...? TTM!?
@@ -735,7 +726,7 @@ todo: TRIAL AND LICENSE KEY / ROCKFISH STUFF
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@ ROADMAP STAGE 7 - REALITY
@@@@@@@@@@@@@@@ ROADMAP STAGE 7 - "REALITY"
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
All in on porting over all the real objects from v7
@@ -748,6 +739,22 @@ todo: Schedule form
todo: can beta test at this point
post installer, enlist trial users get feedback, don't get too down when they shit all over it as they will undoubtedly :)
todo: workorder UI layout stuff (TTM!! Don't re-invent the wheel!)
There's been a lot of ideas about wo floating around and considered, but at the end of the day what we have works so maybe try to meld
into what we have the new concepts and see what comes out. Support a rich wo UI on big screens and scroll around UI on phone maybe.
some notes:
All workorder in one document and just really really tall? (people bitch about RI requiring too many navigation steps to get to shit)
Header and items in one document then bottom in seperate pages?
Is it going to be far easier to code this bitch if I have all the workorder data at hand or..?
How does WBI handle all this because it's kind of the poster child for RAVEN
Workorder is one of those things that may require different views for phone and tablet and laptop etc
Kind of like two views, tiny phone and anything larger
On a PC people will want and expect it to look as much like v7 workorder as possible, maybe that's still a valid layout
just tweaked to work better as a web app a bit but theoretically I could almost duplicate that layout with the tools I have
todo: Documentation
Need to think this through carefully
Need to get the critical bits in for onboarding and importing so people can get going