Hi, I have read back through the achieves of this list and found where Richard Ragan and David Aden discuss how to use versioning with workflows. I have similar issues.
I have an approval workflow which works fine for new content objects. It is a slightly complex workflow with the end result being an active object ready for publishing. So far, so good. The issue arises when an existing object needs to be edited and in put through the same workflow process. I have enabled versioning to a separate versioning database. However there are two problems: 1. We want the published item to remain in place until the edited object is ready to be published. Unfortunately the workflow works on the 'current' object, but we need it to work on the new version. 2. Related to the above problem is that turning the ATTR_ACTIVE flag off does not stop the item from being published. David Aden suggested back in February; "Just design and implement your workflow to always expect to be operating on artifacts in the version DB." He went on to ask if anyone had a more elegant solution - which no one appeared to reply to. Clearly others have dealt with this issue in some way. Hence my post is to try and find some instruction/documentation/example code of how to deal with this. It seems to be a little more complex to implement and undocumented than perhaps it should be. I'd like to avoid 're-inventing the wheel' if possible. Kind Regards Dave Crosby Customer Services Manager ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm ------------------------------------------------------------------------------ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
