The action to take. Must be one of the following: create, delete, get, getAttachments, modify (optional)
Values:
create
delete
deleteAttachments
get
getAttachments
modify
attachmentPath
string
The file path of the directory in which to put the attachments. If the directory does not exist, ColdFusion creates it. If you omit this attribute, ColdFusion does not save any attachments. If you specify a relative path, the path root is the ColdFusion temporary directory, which is returned by the GetTempDirectory function. (optional)
connection
variableName
The name of the connection to the Exchange server, as specified in the cfexchangeconnection tag. If you omit this attribute, and you specify cfexchangeconnection tag attributes in this tag, ColdFusion creates a temporary connection. (optional)
task
any
Required
A reference to the structure that contains the task properties to be set or changed and their values. You must specify this attribute in number signs (#). For more information on the event structure, see the Usage section. (required)
name
string
Required
The name of the ColdFusion query variable that will contain the returned mail messages or information about the attachments that were retrieved. (required)
results
string
(create) The name of a variable that will contain the UID of the task that is created. You use this value in the uid attribute of other actions to identify the task to be acted on. (optional)
uid
string
Required
A case-sensitive Exchange UID value that uniquely identifies the tasks on which to perform the action. For the delete action, this attribute can be a comma delimited list of UID values. The getAttachments and modify action allow only a single UID value. (optional)
result
string
The name of a variable that contains the UID of the task that is created. You use this value in the uid attribute of other actions to identify the task to be acted on.
Examples
Sample code using the cfexchangetask tag
Add an Example for: cfexchangetask
Use this form to create the Serialized JSON string needed to add an example into the docs.