This commit is contained in:
@@ -384,7 +384,7 @@ todo: many biz objects are not using new PUT methodology
|
||||
|
||||
|
||||
|
||||
CURRENTLY DOING:
|
||||
CURRENTLY DOING: misc items below
|
||||
|
||||
MISC WO ITEMS that came up
|
||||
scheduled user conflict is triggering error properly on initial create and save but NOT when edited and saved
|
||||
@@ -393,20 +393,10 @@ MISC WO ITEMS that came up
|
||||
but not showing for exact field or row in grid
|
||||
This is likely occurring with other things, may not have tested this scenario of update and error properly
|
||||
so replicate the fix whatever it is or look for the same issue
|
||||
|
||||
|
||||
Scheduled user selecting rate on new isn't populating rate-viz, (server is on save though)
|
||||
|
||||
|
||||
3720 3: BUMPABLE CASE I THINK prevent double booking a tech (some kind of warning)
|
||||
availability feature??? maybe bump as a new availablity feature where user picks from a popup schedule for that tech?
|
||||
if not maybe a alert from the workorder itself when they save saying double booked??
|
||||
Searching time series and userid is a bit slow maybe or needs custom query not ef able??
|
||||
|
||||
IDEA:
|
||||
global setting allow double booking or not
|
||||
if allowed then no check
|
||||
if not allowed then validation code at server checks and barfs if already booked for that user
|
||||
|
||||
3873 3: subtree woitem lists implement
|
||||
must be some planning on this, forget what I decided exactly
|
||||
|
||||
@@ -1253,7 +1243,13 @@ BUILD CHANGES OF NOTE
|
||||
|
||||
Build 111
|
||||
|
||||
- Notification subscription list now with more detailed info
|
||||
- Notification subscription list now with more detailed info to disambiguate similar subscriptions that vary only in small details
|
||||
|
||||
- Prevent double booking a tech case 3720 customer request
|
||||
global setting "Allow schedule conflicts" and if on will check if same tech is booked already within that time frame on update or new scheduled user record
|
||||
will not check pre-existing or ones where a match can't be made due to null tech, start or stop date
|
||||
implemented as a server validation check so if there is a conflict will balk and return a validation error that will appear under both the scheduled user start and stop date saying "Schedule conflict"
|
||||
|
||||
- Global settings Customer signature widget title, header, footer text fields added and implemented
|
||||
- Signatures on work order implemented
|
||||
Here is how to print them on report:
|
||||
|
||||
Reference in New Issue
Block a user