This commit is contained in:
2022-03-08 18:48:55 +00:00
parent 696f60e166
commit 3fefca8784
2 changed files with 21 additions and 6 deletions

View File

@@ -57,8 +57,11 @@ How to implement auto notifications if can report and send from server
todo: dbutil erase db new tables not added!! may b e more than just customernotification, haven't been in there in a while todo: dbutil erase db new tables not added!! may b e more than just customernotification, haven't been in there in a while
todo: more reportable events likely need to be set as it only has two and sb more see v7 etc
todo: remove these unused fields:
public string Subject { get; set; }//email subject line
public string Message { get; set; }//email body
OTHER B4BETA OTHER B4BETA
copy of customer notification doesn't seem to be implemented, possibly others, do a reference search for each notification and track down any that remain un-implemented. copy of customer notification doesn't seem to be implemented, possibly others, do a reference search for each notification and track down any that remain un-implemented.
@@ -847,6 +850,8 @@ Current v8 docs home: https://www.ayanova.com/docs/
BUILD 8.0.0-beta.1-rc4 CHANGES OF NOTE BUILD 8.0.0-beta.1-rc4 CHANGES OF NOTE
- Many schema updates, must generate new database with this release
- subscriptions lists fixed bug where no type selected would display "[undefined]" in data list, now displays nothing - subscriptions lists fixed bug where no type selected would display "[undefined]" in data list, now displays nothing
- fixed tag control title which was too high and smaller chips so that tag controls are same height as other controls and can show more in a smaller space. - fixed tag control title which was too high and smaller chips so that tag controls are same height as other controls and can show more in a smaller space.
- added missing "duration" field description to notify-subscription docs - added missing "duration" field description to notify-subscription docs
- Added CustomerNotification feature, exposed as Customer notifications in UI Customers section, see corresponding help doc for details

View File

@@ -602,6 +602,7 @@ export default {
} }
}, },
showWorkOrderReportSelector() { showWorkOrderReportSelector() {
//## MUST ALSO UPDATE submit() check for reportable event if add here
switch (this.obj.eventType) { switch (this.obj.eventType) {
case 30: //workorder completed case 30: //workorder completed
return true; return true;
@@ -610,6 +611,7 @@ export default {
} }
}, },
showQuoteReportSelector() { showQuoteReportSelector() {
//## MUST ALSO UPDATE submit() check for reportable event if add here
switch (this.obj.eventType) { switch (this.obj.eventType) {
case 9: //quote status changed case 9: //quote status changed
return true; return true;
@@ -909,9 +911,14 @@ export default {
try { try {
vm.formState.loading = true; vm.formState.loading = true;
window.$gz.form.deleteAllErrorBoxErrors(vm); window.$gz.form.deleteAllErrorBoxErrors(vm);
//don't send the deliveryaddress if it's an in-app notification //don't send the report if it's not reportable (could be set by duplicate option from one that *is* reportable)
if (vm.obj.deliveryMethod == 1) { //## MUST ALSO UPDATE CoreJobCustomerNotify check for reportable event if add here
vm.obj.deliveryAddress = null; switch (vm.obj.eventType) {
case 9:
case 30:
break;
default:
vm.obj.linkReportId = null;
} }
const res = await window.$gz.api.upsert(API_BASE_URL, vm.obj); const res = await window.$gz.api.upsert(API_BASE_URL, vm.obj);
if (res.error) { if (res.error) {
@@ -1167,7 +1174,10 @@ async function fetchTranslatedText() {
"QuoteIntroduction", "QuoteIntroduction",
"QuoteQuoteRequestDate", "QuoteQuoteRequestDate",
"QuoteValidUntilDate", "QuoteValidUntilDate",
"EmailSubject" "EmailSubject",
"CustomerServiceRequestRequestedBy",
"CustomerServiceRequestCustomerReferenceNumber",
"CustomerServiceRequestTitle"
]); ]);
} }