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
2021-03-24 00:08:43 +00:00
parent 827f45df2a
commit 6d0ecb2304
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
ayanova/devdocs/todo.txt
View File

@@ -186,7 +186,7 @@ todo: many biz objects are not using new PUT methodology
CURRENTLY DOING: workorder (status) CURRENTLY DOING: workorder (status), then a bit of research on api structure (see below) then get going from Client end backwards once have rough idea and flesh it out as I go along and refine
todo: workorder status list first, it's a table of created items, keep properties from v7 but add the following properties: todo: workorder status list first, it's a table of created items, keep properties from v7 but add the following properties:
??RolesAllowed - who can select the status (still shows if they can't select but that's the current status, like active does) ??RolesAllowed - who can select the status (still shows if they can't select but that's the current status, like active does)
@@ -226,6 +226,9 @@ todo: workorder global setting of which roles can change a workorder status??
todo: Workorder -> WorkorderService now can combine tables all together under workorder todo: Workorder -> WorkorderService now can combine tables all together under workorder
todo: quick sanity check on how to structure a rest api for a complex object with descendant collections
just to be sure bfore I get too carried away and re-invent the wheel by accident
todo: WorkorderBiz "modernize" follow the norms of other objects todo: WorkorderBiz "modernize" follow the norms of other objects
explicitly decouple the graph from each other, currently I think it's set to force transaction for all graph but in reality it should just be separate objects loosely coupled explicitly decouple the graph from each other, currently I think it's set to force transaction for all graph but in reality it should just be separate objects loosely coupled
Fetchable as an entire graph for reporting and initial loading of UI form but updateable and fetchable separately Fetchable as an entire graph for reporting and initial loading of UI form but updateable and fetchable separately