Editing Automated Email Installation

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
 
'''SME Automatic Outbound Email Event'''
 
'''SME Automatic Outbound Email Event'''
<br>The purpose of this add on program is to automatically notify Techs and Customers of creation/closing
+
<br>The purpose of this add on program is to automatically notified Techs and Customers of creation/closing
 
and scheduling of Service Tickets or Issues within SME. This bundled with the SME ability to handle
 
and scheduling of Service Tickets or Issues within SME. This bundled with the SME ability to handle
 
incoming mail can create a powerful tool for capturing and issuing emails automatically without SME
 
incoming mail can create a powerful tool for capturing and issuing emails automatically without SME
Line 7: Line 7:
  
 
== Requirements ==
 
== Requirements ==
* SME version 7.1 or later
+
SME version 7.1 or later
* SME Web services setup on IIS for incoming mail. SME does not capture emails directly.
+
<br>• SME Web services setup on IIS for incoming mail. SME does not capture emails directly.
* SME Field Scheduler for setup of Incoming and Outgoing Mail
+
<br>• SME Field Scheduler for setup of Incoming and Outgoing Mail
* Admin account in SME must have a valid and working SMTP outgoing email, see [[Email Settings]]
 
* Exclusive Access is Required - All Users Must Be Out of SME
 
  
 
<br>'''Not covered in this add on'''
 
<br>'''Not covered in this add on'''
* Sending Tickets to customer automatically
+
<br>• Sending Tickets to customer automatically
* Email campaigns
+
<br>• Email campaigns
  
  
Line 39: Line 37:
 
== Modifying outbound looks and information Emails ==
 
== Modifying outbound looks and information Emails ==
 
It is possible to modify the outbound emails look and information. If you are interested please notify high5 software.
 
It is possible to modify the outbound emails look and information. If you are interested please notify high5 software.
The automatic outgoing email templates have a few basic rules that, when followed, make it pretty easy to work with:
 
 
You need to have a Subject and a Summary field  - these translate to Email Subject and Email Body in the sent email.
 
-Seen in code as "as Subject" and "as Summary"
 
 
You are pulling from service/Install "a", and customer contact "b" as your available database fields to work with.
 
 
If it's a non-text field (Such as ordernumber, which is a number), you must use:
 
cast([field] as varchar(max))
 
 
Wrap all fields in isnull([field],'') so as not to break the report on null database values.
 
 
Otherwise, you're just writing the email text and adding some simple HTML for formatting.
 
 
<nowiki>
 
'<br>' = new line.
 
</nowiki>
 
 
Sample Template:
 
 
<nowiki>
 
'[' + cast(a.OrderNumber as varchar(max)) + '] for : ' + a.CustName  as Subject,
 
isnull(a.CustName,'') + '<br>' + isnull(a.addressblock, '') + '<br>' + a.Summary' + '<br><br>' + cast(a.ordernumber as varchar(max)) + '<br><br>' + 'Services Performed:' +  '<br>' + isnull(a.ServPerf,'') as Summary
 
</nowiki>
 
 
For a test order with these fields:
 
Custname: TestCust
 
OrderNumber: 200
 
Address: 3243 15th St SomeAddress, SomePlace
 
Services Performed: "Went to the place and did the stuff"
 
Summary: Some Job
 
 
The above template would give you this layout:
 
 
Email Subject:
 
[200] for : TestCust
 
 
Email Body:
 
TestCust
 
3243 15th St SomeAddress, SomePlace
 
Some Job
 
 
200
 
 
Services Performed:
 
"Went to the place and did the stuff"
 
 
 
 
The standard outgoing email format looks like this:
 
 
<nowiki>
 
(case when a.BillingStatUID = 'void' then 'Order VOID'
 
            else (case when isnull(a.OrderStatus, '') = '' then 'Order Open'
 
                        else '' + '' end) end) + ' [' +isnull(cast(a.OrderNumber as varchar(100)), '') + '] ' 
 
                        +': '+ a.CustName + '  - Status Updated By: '+(Select Name From SMPUser Where UserName = a.WhoEdit)
 
                        as Subject, +
 
                       
 
+ '<br/><font size="2" face="verdana" color="black">'
 
+ '<br/>' +
 
+ '<br/> <strong>' +'Customer: '+  a.BillName + '</strong><br/>'
 
+ '<br/>' +
 
+ '<br/>' +'Site Address: '+ '<br/>' +a.CustName
 
+ '<br/>' + a.Address1+', '
 
+ '<br/>' +''+ a.City + ', ' + a.St+' ' +a.Zip
 
+ '<br/>' +
 
+ '<br/>' +'Site Phone : ' + (Select distinct isnull(a.fPhone, '') From CustCont b Where a.contactuid = b.uid)
 
+ '<br/>' +'Contact: '+ (Select distinct b.Name From CustCont b Where b.UID = a.Contactuid) +
 
+ '<br/>' +'Email : ' + (Select distinct isnull(b.Email, '') From CustCont b Where a.contactuid = b.uid)
 
+ '<br/>' +
 
+ '<br/>' +'Service Order Number:  ' +'<strong>'+          coalesce(convert(varchar, a.Ordernumber), '')+'</strong>'
 
+ '<br/>'
 
+ '<br/>' + 'Order Summary: ' + a.Summary+ ' '+
 
+ '<br/>' + 'Taken By:  ' + a.TakenBy+ ' '+
 
+ '<br/>' + 'Open Date/Time: ' +isnull(cast(a.DateTimeIn as varchar(100)),'') +
 
+ '<br/>' + 'Date/Time Due:  ' +isnull(cast(a.DateTimeDue as varchar(100)),'') +
 
+ '<br/>' + 'Order Status:  ' + a.OrderStatus+ ' '+
 
+ '<br/>' + 'Close Date/Time:' +isnull(cast(a.DateTimeClosed as varchar(100)),'') +
 
+ '<br/>' + 'SLA Category: ' + a.SLACategory+ ' '+
 
+ '<br/>' + 'Refrence Number: ' + a.RefNum+ ' '+
 
+ '<br/>' + 'Tech Assigned:  ' + a.AssignedTo+ ' '+
 
+ '<br/><strong>'+'Services Requested:' + '<strong>'
 
+ '<br/>' +isnull(a.ServReq,'')
 
+ '<br/>'
 
+'<div align="center"> <span style="font-size:smaller;"></span></div></font>'
 
as Summary
 
</nowiki>
 

Please note that all contributions to High5Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see High5Wiki:Copyrights for details). Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)