workflow adopting different objects

[Toby Tremayne]

Guys I'm just wondering if anyone else has come across this and whether it's a bug/oversight or if it's supposed to happen this way....   To create an article I have a link on a page which kicks off a PLP. At the completion of the PLP, a workflow is instanciated and it and it's first task are executed.   This all works fine.  The plp is passed an empty object which it saves it's info to, and the workflow creates it's own artifact.   What I had hoped to do was pass the workflow my existing object (which perhaps should be an enhancement request, unless there's actually a way to do it).  However before I got to that stage I discovered that while the workflow was indeed creating it's own separate object, when I got back to my admin page it displayed the contents of the workflow and showed the object CREATED BY THE PLP - *NOT* the 'workflow instance artifact'   What was happening was at the the end of my PLP, I was renaming the workflow instance so it would have the same name as the article.  However in doing so, (using cfa_contentobjectdata to rename the label) it adopted the entire object.    So after the renaming was completed, if I referred to the workflow.artifactinstanceid it was the ORIGINAL object, not the workflow artifact any more.   To fix everything up I've put in a command to delete the workflow instance artifact object, but it just seems to me that that's a little bit daft...  I would have thought I would need to replace the artifact manually, or at least specify a different ID.  All I did was change it's name and it took the object with the same name as it's own artifact.   Any comments guys?  I thought that a bit strange..   Toby     Toby Tremayne Code Poet and Zen Master of the Heavy Sleep Show-Ads Interactive Pty Ltd 359 Plummer St Port Melbourne AUST VIC 3207 +61 3 9245 1247