Can old workflow instances execute new code?

[Florin Wach]

Hi Judy,

yes, the running workflows will keep their definition. When transporting a definition into a new system, the target system will create a new internal runtime version when there's any workflow existing for the current version (which is obsiously the case - you can see these numbers in the workflow builder on the top-left window section).
This feature isn't working like that on the same system with different clients, which explains that you haven't encountered that in the DEV system.

Maybe you could try to put your fix into the coding of a Business Object or create a check-function module on the level of the event-item that could filter your "bad" data. Both would effect immediatly running workflows.

With the very best wishes,
   Florin


-------- Original-Nachricht --------
> Datum: Fri, 1 Jun 2012 14:26:00 -0400
> Von: "Alfano, Judy \\(ISO\\)" <JAlfano2 at massmutual.com>
> An: sap-wug at mit.edu
> Betreff: Can old workflow instances execute new code?

> Hi All - We have a custom workflow that initially sends an error
> notification to users, followed by a loop wherein each time the deadline
> is met it checks some criteria and decides whether or not to escalate
> the notification to the next level of folks. Currently we have 1000's of
> these escalating daily in production due to invalid triggering event
> container data. So far, support has been unable to identify the
> circumstances that are resulting in the bad event container data. As a
> workaround I decided to insert a condition step that checks for the
> invalid scenario, and if found change the workflow status to complete
> and exit. I put this new condition step in the loop thinking that as the
> next deadline was met for each in-process workflow, it would find the
> error and complete the workflow, taking care of the cleanup of the mess
> in production. I purposely didn't generate a new version when I made the
> change, thinking this would cause the in-process instances to hit the
> new step the next time the loop looped.
> 
>  
> 
> This worked as I expected in our development client where the change was
> made, and in another DEV client after I executed SWU_OBUF. But when I
> transported the change to the QA environment, the in-process workflows
> continue to execute the loop as it was before the code change. I
> executed SWU_OBUF, probably unnecessarily based on the last
> synchronization time - didn't help. 
> 
>  
> 
> Was I just wrong in my thinking that by not generating a new version of
> the workflow, in-process instances would begin executing the changed
> code the next time they hit the loop? 
> 
>  
> 
> Thanks very much for your help!
> 
>  
> 
> Judy Alfano
> USIG, B&TS
> MassMutual Financial Group
> 1295 State Street  MIP W361 
> 
> Springfield MA 01111
> 
> 413-744-2428
> 
> P Please consider the environment before printing this e-mail 
> 
> 
> 
> 
> This e-mail transmission may contain information that is proprietary,
> privileged and/or confidential and is intended exclusively for the person(s) to
> whom it is addressed. Any use, copying, retention or disclosure by any
> person other than the intended recipient or the intended recipient's designees
> is strictly prohibited. If you are not the intended recipient or their
> designee, please notify the sender immediately by return e-mail and delete all
> copies.