Creates, deletes, modifies, and gets Microsoft Exchange contact records, and gets contact record attachments.
ColdFusion 10: Added the attribute serverVersion.
ColdFusion 8: Added this tag.
Note: If you omit the connection attribute, create a temporary connection by specifying cfexchangeconnection tag attributes in the cfexchangecontact tag. In this case, ColdFusion closes the connection when the tag completes. For details, see the cfexchangeconnection tag open action. |
Note: You can specify this tag's attributes in an attributeCollection attribute whose value is a structure. Specify the structure name in the attributeCollection attribute and use the tag's attribute names as structure keys. |
cfexchangecalendar, cfexchangeconnection, cfexchangefilter, cfexchangemail, cfexchangetask, Interacting with Microsoft Exchange Servers in the Developing ColdFusion Applications
Attribute |
Action |
Req/Opt |
Default |
Description |
---|---|---|---|---|
action |
N/A |
Required |
|
The action to take. Must be one of the following values:
|
attachmentPath |
getAttachments |
Optional |
|
The absolute filepath of the directory in which to put the attachments. If the directory does not exist, ColdFusion creates it. |
connection |
all |
Optional |
|
The name of the connection to the Exchange server, as specified in the cfexchangeconnection tag. If you omit this attribute, create a temporary connection by specifying cfexchangeconnection tag connection open action attributes in the cfexchangecontact tag. |
contact |
createmodify |
Required |
|
A reference to the structure that contains the contact properties to be set or changed and their values. Specify this attribute in number signs (#). |
generateUniqueFilenames |
getAttachments |
Optional |
no |
A Boolean value that specifies whether to generate unique filenames if multiple attachments have the same filenames. If two or more attachments have the same filename and this option is yes, ColdFusion appends a number to the filename body (before the extension) of any conflicting filenames. Thus, if three attachments have the name myfile.txt, ColdFusion saves the attachments as myfile.txt, myfile1.txt, and myfile2.txt. |
name |
getgetAttachments |
Required |
|
The name of the ColdFusion query variable that contains the returned contact records or information about the attachments that were retrieved. For more information on the returned data, see Usage. |
result |
create |
Optional |
|
The name of a variable that contains the UID of the contact that is created. Use this value in the uid attribute of other actions to identify the contact to be acted on. |
serverVersion |
|
Optional |
2007 |
Specifies the Microsoft Exchange Server version. The values are:
|
uid |
getAttachmentsdeletemodify |
Required |
|
A case-sensitive Exchange UID value that uniquely identifies the contacts on which to perform the action. For the delete action, this attribute can be a comma-delimited list of UID values. The deleteAttachments, getAttachments, and modify actions allow only a single UID value. |
When you specify the create or modify action, the contact attribute must specify a structure that contains information that defines the events. The structure can have the following elements. Include only the elements that you are setting or changing.
Assistant |
Attachments |
BusinessAddress |
BusinessFax |
BusinessPhoneNumber |
Categories |
Company |
Department |
Description |
DisplayAs |
Email1 |
Email2 |
Email3 |
FirstName |
HomeAddress |
HomePhoneNumber |
JobTitle |
LastName |
MailingAddressType |
Manager |
MiddleName |
MobilePhoneNumber |
NickName |
Office |
OtherAddress |
OtherPhoneNumber |
Pager |
Profession |
SpouseName |
WebPage |
|
|
All fields except the BusinessAddress, HomeAddress, and OtherAddress fields contain text; the three address fields must contain structures with the following text fields:
The cfexchangecontact tag manages contact records on the Exchange server. Use the cfexchangecontact tag to perform the following actions:
Use the following syntax to specify an in-memory attachmentPath directory. In-memory files are not written to disk and speed processing of transient data.
attachmentpath = "ram:///filepath" |
The path can include multiple directories, for example ram:///petStore/orders/messageAttachments. Create all directories in the path before you specify the file. For more information on using in-memory files, see Working with in-memory files in Optimizing ColdFusion applications in the Developing ColdFusion Applications.
When you specify the delete action you must specify a uid attribute with a comma-delimited list of one or more Exchange UIDs that identify the contacts to delete. You can use the get action, with an appropriate filter expression, to determine the UID values to specify.
If all UIDs that you specify are invalid, the cfexchangecontact tag generates an error. If at least one UID is valid, the tag ignores any invalid UIDs and deletes the items specified by the valid UID.
When you specify the get action, the query object specified by the name attribute contains one record for each retrieved contact. The query object has columns with the same names and data formats as the fields listed for the contact attribute structure, with the following changes:
When you use the getAttachments action, specify a single UID and a name attribute. The cfexchangecontact tag populates a query object with the specified name. Each record has the following information about an attachment to the contact specified by the UID:
Column name |
Description |
---|---|
attachmentFileName |
The filename of the attachment. |
attachmentFilePath |
The absolute path of the attachment file on the server. If you omit the attachmentPath attribute, this column contains the empty string. |
CID |
The content-ID of the attachment. Typically used in HTML img tags to embed images in a message. |
mimeType |
The MIME type of the attachment, such as text/html. |
isMessage |
A Boolean value specifying whether the attachment is a message. |
size |
The attachment size in bytes. |
The tag places the attachments in the directory specified by the attachmentPath attribute. If you omit the attachmentPath attribute, ColdFusion does not get any attachments, it gets the information about the attachments. This lets you determine the attachments without incurring the overhead of getting the attachment files.Use the following syntax to specify an in-memory attachmentPath directory. In-memory files are not written to disk and speed processing of transient data.
attachmentpath = "ram:///path" |
The path can include multiple directories, for example ram:///petStore/orders/messageAttachments. Create all directories in the path before you specify the file. For more information on using in-memory files, see Working with in-memory files in Optimizing ColdFusion applications in the Developing ColdFusion Applications.
The getAttachments action works only if authentication for EWS (Exchange Web Services) is set to basic in the server setup of Exchange. IWA (Integrated Windows Authentication) is not supported.
If you specify the modify action, the uid attribute must specify a single Exchange UID. The contact structure must specify only the fields that you are changing. Any fields that you do not specify remain unchanged.
If a contact has attachments and you specify attachments when you modify the contact, the new attachments are added to the previous attachments, and do not replace them. Use the deleteAttachments action to remove any attachments.
The following example lets a user enter information in a form and creates a contact on the Exchange server with the information:
<!--- Create a structure to hold the contact information. ---> <cfset sContact="#StructNew()#"> <!--- A self-submitting form for the contact information ---> <cfform format="flash" width="550" height="460"> <cfformitem type="html"><b>Name</b></cfformitem> <cfformgroup type="horizontal" label=""> <cfinput type="text" label="First" name="firstName" width="200"> <cfinput type="text" label="Last" name="lastName" width="200"> </cfformgroup> <cfformgroup type="VBox"> <cfformitem type="html"><b>Address</b></cfformitem> <cfinput type="text" label="Company" name="Company" width="435"> <cfinput type="text" label="Street" name="street" width="435"> <cfinput type="text" label="City" name="city" width="200"> <cfselect name="state" label="State" width="100"> <option value="CA">CA</option> <option value="MA">MA</option> <option value="WA">WA</option> </cfselect> <cfinput type="text" label="Country" name="Country" width="200" Value="U.S.A."> <cfformitem type="html"><b>Phone</b></cfformitem> <cfinput type="text" validate="telephone" label="Business" name="businessPhone" width="200"> <cfinput type="text" validate="telephone" label="Mobile" name="cellPhone" width="200"> <cfinput type="text" validate="telephone" label="Fax" name="fax" width="200"> <cfformitem type="html"><b>Email</b></cfformitem> <cfinput type="text" validate="email" name="email" width="200"> </cfformgroup> <cfinput type="Submit" name="submit" value="Submit" > </cfform> <!--- If a form was submitted, populate the contact structure from it. ---> <cfif isDefined("Form.Submit")> <cfscript> sContact.FirstName=Form.firstName; sContact.Company=Form.company; sContact.LastName=Form.lastName; sContact.BusinessAddress.Street=Form.street; sContact.BusinessAddress.City=Form.city; sContact.BusinessAddress.State=Form.state; sContact.BusinessAddress.Country=Form.country; sContact.BusinessPhoneNumber=Form.businessPhone; sContact.MobilePhoneNumber=Form.cellPhone; sContact.BusinessFax=Form.fax; sContact.Email1=Form.email; </cfscript> <!--- Create the contact in Exchange ---> <cfexchangecontact action="create" username ="#user1#" password="#password1#" server="#exchangeServerIP#" contact="#sContact#" result="theUID"> <!--- Display a confirmation that the contact was added. ---> <cfif isDefined("theUID")> <cfoutput>Contact Added. UID is#theUID#</cfoutput> </cfif> </cfif> |
Sign in to your account