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-08-05 00:57:09 +00:00
parent 78e640f2d3
commit 7488e73d8d
2 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
ayanova/devdocs/todo.txt
View File

@@ -532,6 +532,11 @@ todo MISC:
Notification code from workorder/quote/pm *item* grandchildren? Why is this a thing? shouldn't it be removed entirely, it's jsut wasted cpu cycles Notification code from workorder/quote/pm *item* grandchildren? Why is this a thing? shouldn't it be removed entirely, it's jsut wasted cpu cycles
can a user even subscribe to any of these? Should they? can a user even subscribe to any of these? Should they?
check that jobs don't run during seeding check that jobs don't run during seeding
see if server jobs are staggered (i.e. don't run at the same time)
maybe set the repeat interval off by a small amount so they can't sync up?
or maybe they just run sequentially from the initial trigger anyway?
But even so, staggering the repeat interval will mean less jobs running in the same overall job cycle
ITEMS section of workorder form needs to stand out somehow more, maybe a splash of color in the icon or something ITEMS section of workorder form needs to stand out somehow more, maybe a splash of color in the icon or something
profit$ profit$

3
ayanova/src/views/ay-data-list-column-view.vue
View File

@@ -442,7 +442,8 @@ function initWorkingView(vm) {
//Pass 1, iterate the columns first //Pass 1, iterate the columns first
for (let i = 0; i < columns.length; i++) { for (let i = 0; i < columns.length; i++) {
let fld = vm.fieldDefinitions.find(z => z.fieldKey == columns[i]); let fld = vm.fieldDefinitions.find(z => z.fieldKey == columns[i]);
//bugbug: if there is a incorrect field in the view it surfaces here when user attempts to set the column view because it doesn't turn up so fld here will be null
//in this case ideally the fix would be to ignore the probably bogus column and move on to work without it
let o = { let o = {
key: fld.fieldKey, key: fld.fieldKey,
title: null, title: null,