Liz,

Custom rules must be placed in /project_folder/packages/rules with the 
naming convention that you are using (rule[TypeName].cfc).  The display 
code does indeed go inside the execute function within the cfc.  I'm 
sure you'd be able to include .cfm files into that function if necessary.

About your second question, I think some code would be helpful.  You can 
use #application.url.conjurer#?objectid=<some object id>. 

Fixing #1 might also fix #2 in this case.  Create the rule in the 
correct directory, go to Admin -> COAPI Management and deploy the new 
rule, then see what heppens with the display.

-Jake

Elizabeth wrote:
> Hi
> I have a few qus (again :-)) about custom rules and display of the
> elements they concern.
>
> Firstly am i right in thinking that the display code for custom rules
> is contained solely within the execute function in the
> ruleMyCustomType.cfc?  Or can it be stored elsewhere? Are the display
> files in webskin/myCustomType/ simply to provide a displaymethod
> listing or can they be pulled in in some way?
>
> Secondly when i attempted to create links within my rules display code
> they led to a page with the message 'unknown type'. I was using the
> variable application.url.conjurer setup. Do I need to create my own
> rulespecific code? I notice that the relevant reords in the refobjects
> table stored the rule name rather than the type. is this correct?
>
> Sorry If these are obvious qus but i need to get up to speed on some of
> this stuff fairly sharpish.
>
> Regards
> Liz
>
>
> >
>
>   

-- 
Jake Churchill
CF Webtools
11204 Davenport, Ste. 200b
Omaha, NE  68154
http://www.cfwebtools.com
402-408-3733 x103



--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups 
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to