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 14:39:37 +00:00
parent 31ef6db26e
commit 8d0f53ce54
2 changed files with 2 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
ayanova/devdocs/todo.txt
View File

@@ -189,17 +189,13 @@ todo: many biz objects are not using new PUT methodology
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 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:
SelectRoles - who can select the status (still shows if they can't select but that's the current status, like active does) SelectRoles - who can select the status (still shows if they can't select but that's the current status, like active does)
This is best handled at the client. It prefetches all the status out of the normal picklist process, more like how other things are separately handled now without a picklist This is best handled at the client. It prefetches all the status out of the normal picklist process, more like how other things are separately handled now without a picklist
client then knows if a status is available or not and can process to only present available ones client then knows if a status is available or not and can process to only present available ones
Server can use a biz rule to ensure that it can't be circumvented Server can use a biz rule to ensure that it can't be circumvented
DeselectRoles - who can unset this status (important for process control) DeselectRoles - who can unset this status (important for process control)
FinishedStatus bool - this is a final status indicating all work on the workorder is completed, affects notification etc FinishedStatus bool - this is a final status indicating all work on the workorder is completed, affects notification etc
when set this, lock is checked in UI automatically and they need to remove it to force unlock and final when set this, lock is checked in UI automatically and they need to remove it to force unlock and final
LockWorkorder - this status is considered read only and the workorder is locked LockWorkorder - this status is considered read only and the workorder is locked
Just a read only thing, can just change status to "unlock" it Just a read only thing, can just change status to "unlock" it
to support states where no one should work on a wo for whatever reason but it's not necessarily completed to support states where no one should work on a wo for whatever reason but it's not necessarily completed

2
ayanova/src/api/notifypoll.js
View File

@@ -7,7 +7,7 @@ export default {
return; return;
} }
keepChecking = true; keepChecking = true;
//initial delay so it fetchs "immediately" //initial delay so it fetches "immediately"
let pollingInterval = 3000; let pollingInterval = 3000;
let status = null; let status = null;
while (keepChecking == true) { while (keepChecking == true) {