>Maybe an alternative would be to provide an object type to >getObjectApprovers - although I am guessing there are just a few minor >differences between News and Objects that made the distinction >necessary.
Yup. I agree. If we have to introduce a new method to workflow for each new/custom type we're in big trouble. This unexpected behavior has put me in a bit of a pickle and I'm looking for a quick way out. >If each object type has different rules for working out who >can approve >then maybe the basic types need to be extended with a "getApprovers" >method that can be specific for each type? At first glance that sounds like it might do the trick. Of course I don't know how this will play with Daemon's future workflow plans. Daemon, whatcha reckon? ~Tom --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
