Sub-workflow version problems

[Mike Pokraka]

Hi Rick,

That's how it would work. A subwf is a completely new instance of a WF.

There may be a way to call a WF with a specific version, perhaps someone
else has hacked this. But for incompatible changes to a subWF it's usually
far easier to make a copy and include that in your new version of the main
WF. For reporting purposes it's usually not a biggie.

Regards,
Mike


On Wed, March 14, 2012 12:42 am, Rick Bakker wrote:
> Hello,
>
> Could someone confirm/deny:
>
> 1. Workflow A calls sub-workflow B.
> 2. If you change sub-workflow B then existing instances of A will call
>    the new version of B.
>
> I didn't expect this and it can cause some big problems, e.g. if you
> change
> the binding between A and B then A can even go into error when it tries
> to call B.
>
> Does anyone know a way to get A to call the version of B that was live
> when
> the instance of A was created?
>
> Be careful when changing sub-workflows!
>
> (I knew of this problem with Tasks but that's fair enough, they don't have
> versions)
>
> regards
> Rick Bakker
> hanabi technology
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>