ATC: SEND FROM email  TO email  SUBJ text; BODY variable options

This command sends an email to the person or persons specified. “Route Via” is not relevant and contacts without email addresses are ignored.

  • FROM email is optional. email can be specified as described below; however only a single email address is supported. If there are multiple email addresses, the final one is used. If FROM is not specified, the default is the ATC-monitored email address.  Note that the Web Application must have SMTP permission to “send as” the specified email account, which is typically not the case.
  • TO email is required. The command can include multiple TO clauses. The email can be specified as any of the following:
    • * indicates the email addresses of all routees on the current sequence.
    • RouteSeq is any integer indicating a route sequence. The email will be sent to the email addresses of all routees at the specified sequence.
    • name@domain.com is any specific email address or several addresses separated by semicolons (but no spaces).
    • Alias.field is any tablename.fieldname that contains a contact key or email address, used to determine the person(s) whose email addresses will be used (for example, DocMeetingAttendee.UserKey).
    • $var is any variable defined through a previous ATC: SET or ATC: SETHTML command that contains an email address or addresses separated by a semicolon.
  • SUBJ text; is optional but, if specified, must end with a semicolon. It defines the email’s subject line. text has a limit of 80 characters and cannot include > < or & but can include replacement bookmarks such as [table_fieldname]. The required semicolon signifies the end of the text and will not be included in the email’s subject.
  • BODY variable is required.  variable is any variable defined through a previous ATC: SET or ATC: SETHTML command that contains the body of the email.
  • options are optional. There are several options that can be used singularly or together, separated by spaces.
    • CC email lists the email addresses that will receive the email as “CC”. email can be specified as described above.
    • BCC email lists the email addresses that will receive the email as “BCC”. email can be specified as described above.
    • TRACK OFF turns off tracking of the email.   Otherwise the ATC monitored email address is automatically included in the CC list.
    • AUTOGENERATED NO should be included if you want to suppress the RFC 3834 auto-submitted, auto-generated header that is included automatically.

Example

ATC: SETHTML $Body = Sorry for the delay. Here are my notes: [DocRevision_Notes]
ATC: SEND TO JohnSmith@Acme.com;JoeShmoe@gmail.com TO DocMasterDetail.SourceContact
     SUBJ About [DocHeader_Title];
     BODY $Body

The above example means “first, define the variable $Body to contain ‘Sorry for the delay. Here are my notes:’ followed by whatever is in the DocRevision.Notes field on the document, then create an email with all that text as the body and ‘About’ followed by the title of the document as the Subject and send it to JohnSmith@Acme.com, JoeShmoe@gmail.com and to the email of whoever the Source Contact of the document is.”   The generated email, and all ‘Reply All” responses, will appear as attachments on the document as they are received by sfATC.



Last updated: October 16, 2017 at 14:17 pm; V2017+ green text = new