ColdFusion MX 7 Features

Explore the features that made MX 7 distinctive: Application.cfc, document/report generation, rich forms, web services, and event gateways.

Application.cfc

MX 7 introduced Application.cfc, giving applications named lifecycle methods for application, session, request, error, and missing-template events.

The application framework guide contains a complete tag-based example.

PDF and Document Generation with cfdocument

<cfdocument format="pdf" filename="#ExpandPath('./exports/ticket-summary.pdf')#" overwrite="yes">
    <cfoutput>
        <h1>Ticket Summary</h1>
        <p>Generated #DateFormat(Now(), "mm/dd/yyyy")#</p>
        <p>Open tickets: #openTickets.recordCount#</p>
    </cfoutput>
</cfdocument>

HTML-to-document conversion made reports and printable output approachable. Exact CSS support and rendering behavior are tied to the old engine, so preserve representative output when migrating.

Report Builder and cfreport

ColdFusion Report Builder provided a visual report-design workflow. A template could supply a query to a report definition and render formats such as PDF, FlashPaper, RTF, or other supported outputs depending on the release and configuration.

<cfreport
    template="reports/open-tickets.cfr"
    format="pdf"
    query="#openTickets#">

Flash Forms and XForms

MX 7 could generate richer forms from cfform using Flash or XForms formats. These features are historically important because they reflect the Macromedia product ecosystem, but they are not a sensible basis for a current public application.

<!--- Historical example only --->
<cfform name="customerForm" format="flash" action="save-customer.cfm">
    <cfinput name="name" type="text" label="Customer Name" required="yes">
    <cfinput name="submitButton" type="submit" value="Save">
</cfform>

CFC Web Services

A method marked remote could be exposed through supported remote mechanisms, including SOAP web services.

<cfcomponent output="false">
    <cffunction name="getTicketStatus" access="remote" returntype="string" output="false">
        <cfargument name="ticketId" type="numeric" required="true">

        <!--- Authenticate, authorize, validate, and query. --->
        <cfreturn "open">
    </cffunction>
</cfcomponent>

Do not assume that an old WSDL endpoint is private. Inventory every remote method and every consumer before changing or disabling it.

Event Gateways

ColdFusion MX 7 Enterprise added event gateways for asynchronous or non-HTTP events. Deployments could integrate with messaging, instant messaging, SMS, directory watching, and custom Java gateway types.

XML and Integration

MX-era ColdFusion applications commonly parsed XML, called SOAP services, created Java objects, and connected to directory or messaging systems. These integrations often fail first during migration because they depend on old certificates, protocols, schemas, drivers, or vendor endpoints.

Preservation Checklist for MX 7 Features

• Save sample PDFs and reports for visual comparison.
• Export or document report definitions and fonts.
• Inventory every remote CFC method and WSDL consumer.
• Record event gateway instances and listener components.
• Capture form screenshots before replacing Flash/XForms interfaces.
• Document Administrator-only mappings, tasks, and service settings.
• Test output on the exact MX 7 updater used by the original application.