|
Tuesday 01 July 2003 9:48:29 am
Hello, Maybe I missed some essentials about workflows/triggers (being an absolute beginner on this), mainly when and where they are executed: - triggers are used per module/function, no way to discriminate between different parts of your site (be it sections, node trees, ...), it appears one should do this in the workflow => I think it would be much more logical and powerful to select sections/nodetrees and classes with the triggers ("create new trigger for section a if an object of class b is created by user c"). - to handle different parts differently (sounds logical?), you you should filter with the multiplexer event type which is limited to sections and classes (however, failed to do this in 3.1 for even launchhing a one event workflow, maybe a bug, not sure yet) => This creates a huge super-workflow which contains all the different workflows for different (unrelated) functionalities. Somehow, I feel/think triggers are in the wrong place when they are limited to global module/actions (pre and post). Any thoughts from more experienced people on this matter? --paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
