>I don't put much stock in reusing
>applications as a custom tag. If others are doing it, I think it would be
>very interesting to hear about.
I've only used one "mini-app" as a custom tag but it worked out perfectly in
a legacy CF app. A distribution list builder was my first Fusebox app and
is available as either an interactive application module or as a custom tag
for creating default lists. This is how it runs as three custom tags:
<!--- By default ORT ALWAYS has a dist list created and populated w/
the PITS_ORT list --->
<cfif FORM.failure_stn EQ "ORT/Reliability">
<!--- Create Dist List and... --->
<cfmodule
template="../index_DistList.cfm"
fuseaction="AddDistList"
DistListName="PITS_FA_#facar_no#"
mode="quiet"
>
<!--- ...add default users and... --->
<cfmodule
template="../index_DistList.cfm"
fuseaction="AddDefaultList"
DistListName="PITS_FA_#facar_no#"
DefaultList="PITS_ORT"
mode="quiet"
>
<!--- ...send update email --->
<cfmodule
template="../index_DistList.cfm"
fuseaction="SendUpdate"
module="FA"
no="#facar_no#"
failure_stn="#FORM.failure_stn#"
failure_desc="#FORM.manual_fdesc#"
comments="#FORM.comments#"
update_by_username="#login.username#"
update_by_email="#login.email#"
DistListName="PITS_FA_#facar_no#"
model_desc="#variables.model_desc#"
maillevel="#FORM.fa_level#"
mailstate="ADDED"
mode="quiet"
>
</cfif>
Or just once to send an update to the associated list.
Looking back at this whole thing, I can see about a dozen things I would
write totally different now. Oh well, first time's always a little awkward.
-Alan
Alan Richmond
EDS Denver Solution Centre
Maxtor Corp. Account
Web Application Developer
[EMAIL PROTECTED]
[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
