Input
For more information about mapping and transforming input data, see TIBCO ActiveMatrix BusinessWorks™ Process Design.
The input for the activity is the following.
Input Item |
Datatype |
Description |
username |
string |
Username to use when authenticating to the mail server. Note: The mail server must be configured to require authentication for sending mail. If the mail server is not configured to require authentication, the username and password elements are ignored.
|
password |
string |
Password to use when authenticating to the mail server. |
from |
string |
The email address of the sender. |
to |
string |
The recipient list for the email. This is a repeatable element, so that you can send mail to more than one recipient. You can also supply a list of recipients in a single string by using either a comma or a semicolon (but not both in the same string) to separate the recipients. |
cc |
string |
The cc (carbon copy) list for the email. This is a repeatable element, so that you can place more than one recipient on the CC list. You can also supply a list of CC recipients in a single string by using either a comma or a semicolon (but not both in the same string) to separate the CC recipients. |
bcc |
string |
The bcc (blind carbon copy) list for the email. This is a repeatable element, so that you can place more than one recipient on the BCC list. You can also supply a list of BCC recipients in a single string by using either a comma or a semicolon (but not both in the same string) to separate the BCC recipients. |
replyTo |
string |
The reply to list for the email. This is a repeatable element, so that you can place more than one recipient on the reply to list. You can also supply a reply to list in a single string by using either a comma or a semicolon (but not both in the same string) to separate the addresses in the list. |
subject |
string |
The subject of the email. |
sentdate |
string |
The date stamp for the email. Note: The email server supplies the actual date stamp for the email, so this input item is ignored. This item is deprecated and may be removed in a future release. Do not attempt to place a value in this input item.
|
Fields available when the Upgrade Configuration field is checked |
||
bodyElement |
complex |
This element contains a choice element. You can either supply the bodyText element or the fileName element. The bodyText element is a string containing the body of the message. The fileName element is the path and name of a file containing the body of the message. |
Headers |
complex |
This element contains the schema you defined on the Input Headers tab. You can specify custom headers for outgoing mail messages. You can specify any standard header supported by the If you want to use attachments, make sure the Content-Type header is specified as |
mimeEnvelope |
complex |
This element contains the message attachments. This element contains a repeating element named mimePart that contains each mime attachment. |
mimeHeaders |
complex |
This element contains the mime header for each mimePart. Mime headers can contain the following information:
other mime header information For more information about MIME headers and their syntax, see http://www.faqs.org/rfcs/rfc2045.html. Note: When the content type is specified as "text/*" (for example, "text/xml"), the attachment content is expected to be in either the textContent input element or the file name storing the attachment is expected to be in the fileName input element. When the content type is anything other than "text/*", the attachment content is expected to be in either the binaryContent input element or the file name storing the attachment is expected to be in the fileName input element.
|
binaryContent | textContent | fileName |
choice |
This element contains the mime attachment. The element can be one of the following:
|
Fields available when the Upgrade Configuration field is unchecked |
||
bodyText |
string |
The text of the email message. |
attachmentNames |
string |
A list of names for each attachment to the message. These names are typically the file names of the attachments. Note: The attachmentNames and attachmentData elements are corresponding lists. That is, for each item in the attachmentName element, there must be a corresponding item in the same position in the attachementData list. For example, if there are three attachments, both elements must contain three items and item in the attachmentNames element corresponds to the element in the same position in the attachmentData list.
|
attachmentData |
binary |
A list of attachments to the message. |
contentType |
string |
The MIME content type for the message. You can specify a character encoding in this element for the encoding of the body of the message. |