How about a nice simple solution. Just design and implement
your workflow to always expect to be operating on artifacts
in the version DB. Maybe there is some reason why this
won't work for you. Even if you had a new object, you can
quickly copy it to the version DB before starting the WF.
Rich
> I have a questions about the details of how to use the version API with
> workflows in 1.5 as I'm spec'ing an app now. Following is a description of
> what I want to do:
>
> Take an existing piece of content and kick off a workflow to manage it.
>
> When the workflow starts, create a version called "WorkInProgress" which is
> the actual object I'm going to manage.
>
> Here's the issue -- I want that version to be the artifact that is handled
> by the workflow. But if I specify the UUID of the original object as the
> artifact then the workflow will invoke the edit method on that original
> object -- which is NOT what I want to edit.
>
> If I specify the UUID of the version as the artifact, I'm guessing the WF
> won't be able to find it because the version lives in the version DB, not
> the application DB.
>
> One way to handle this, although it seems a bit kludgey, would be to create
> a special edit method that uses the ObjectID of the original object to get
> the WorkInProgress version and then edit that. This involves a relatively
> unnecessary get of the original object.
>
> Is there another, better way to do this?
>
> David
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.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.
