This commit is contained in:
@@ -382,9 +382,12 @@ todo: many biz objects are not using new PUT methodology
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
CURRENTLY DOING:
|
CURRENTLY DOING: Signature boilerplate text from global settings
|
||||||
|
maybe store in global first fetch or cache if needed only??
|
||||||
|
won't change much but most people won't need it either
|
||||||
|
can I fetch it on first wo open like the rest of the bundle?? somehow?
|
||||||
|
|
||||||
|
|
||||||
update all dependencies front and back
|
|
||||||
|
|
||||||
todo 3: signature: report helper display signature and form ui control to capture /display signature
|
todo 3: signature: report helper display signature and form ui control to capture /display signature
|
||||||
for both tech and customer
|
for both tech and customer
|
||||||
@@ -395,6 +398,8 @@ todo 3: signature: report helper display signature and form ui control to captur
|
|||||||
also, depending on ease, it might make sense to have v8 server check type of image i.e. does it start with svg or not and
|
also, depending on ease, it might make sense to have v8 server check type of image i.e. does it start with svg or not and
|
||||||
then auto convert if necessary.
|
then auto convert if necessary.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
3720 3: BUMPABLE CASE I THINK prevent double booking a tech (some kind of warning)
|
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?
|
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??
|
if not maybe a alert from the workorder itself when they save saying double booked??
|
||||||
|
|||||||
Reference in New Issue
Block a user