Fuseaction
A fuseaction is a request handler. When a Circuit gets a request to perform some action, it receives the request in the form of a fuseaction. A fuseaction is passed or defined for every request the user makes to the application.
A Fuseaction executes one or more fuses. Pre Fusebox 4, Fuses were simply individual CFML pages in ColdFusion. Since the introduction of the circuit XML files to Fusebox, a Fuseaction can now perform quite a bit of functionality without the need of a .cfm file.
Fusebox requests are made of the server through a central controller called index.cfm. This is the central channel through which all requests pass and that contains several fuseaction methods. (more about request processing)
Here, central controller is index.cfm and it receives the fuseaction message of document.login.
Document is the circuit name and login is the fuseaction name.
Fuseactions Control Flow
If the user wants your application to run the "main" fuseaction, the request that follows will do it. The
One job that the core file has is to take any incoming Fuseaction variable, no matter what the scope is, and copy the second part of it (after the dot) into a variable called fusebox.fuseaction. Referencing fusebox.fuseaction is similar to referencing
Instead of needing two
Every time index.cfm (or whatever your default web document is) is run, it expects the variable fuseaction to be passed in.
Default Fuseaction
Fusebox needs a default fuseaction. Default fuseactions are key to understanding how a Fusebox application responds. You set a default fuseaction in the root fbx_settings.cfm file (earlier versions) or in fusebox.xml.cfm (later versions)