Binding issues after transport to production

[Dart, Jocelyn]

Carolyn, 

You do have to be cognisant that not everything in a workflow is version
dependent - particularly the workflow container.  So if you are already
generating versions and doing the other stuff correctly as you seem to
be doing, you need to think about how you are approaching changes to the
container in particular and any other non-version-dependent areas such
as event linkage. 

In particular you should not delete container elements that are no
longer to be used - better to change their description to "Do Not Use"

Also if you have change the structure underlying a container element you
may need to be careful.  If possible, it might be worth considering
creating a new container element. 

If your changes are significant you should also consider the option of
creating a new workflow template and retiring the old workflow template
by deactivating the event linkage to the old template - this will still
let old instances run through to completion.

Hope that helps in your thinking... 

Regards,
Jocelyn  

-----Original Message-----
From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On Behalf
Of Carolyn Fuller
Sent: Thursday, 12 February 2009 11:10 AM
To: SAP Workflow Users' Group
Subject: Re: Binding issues after transport to production

Jocelyn,

I do generate version before modifying the workflows in development.

We do our production validations on workflow transports before midnight.

I take this to mean that if a workflow's binding is working properly  
in our QA environment, then SWU_OBUF should clear up any binding  
issues after a transport to production?

Carolyn
On Feb 11, 2009, at 5:55 PM, Dart, Jocelyn wrote:

> Hi Carolyn,
>
> A) Please STOP DOING THAT! You are just asking for trouble...
>
> B) Yes - run SWU_OBUF after transports ***** OR **** make sure you
> transports go in before midnight system time - as the relevant buffers
> will be automatically refreshed at that time.
>
> C) Even better, when you are modifying workflows make sure you  
> GENERATE
> VERSION before modifying - this keeps changes in the new version of  
> the
> workflow separate from the old version to minimize possible conflicts,
> allowing existing workflows to continue using the old version, while  
> new
> instances use the new version.
>
> Regards,
> Jocelyn
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On  
> Behalf
> Of Alon Raskin
> Sent: Thursday, 12 February 2009 8:16 AM
> To: SAP Workflow Users' Group
> Subject: RE: Binding issues after transport to production
>
> Just to clarify, you are modifying the workflows directly in the
> production system?
>
> Alon Raskin
> e: araskin at 3i-consulting.com
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On  
> Behalf
> Of Carolyn Fuller
> Sent: Wednesday, February 11, 2009 2:17 PM
> To: SAP Workflow Users' Group
> Subject: Binding issues after transport to production
>
> Hi all,
>
> On a couple of occasions I've moved modified workflows from our
> development environment to our QA environment with no problems only to
> encounter binding issues in production. On these occasions, deleting
> the bindings in production and re-creating them in production has
> solved the problem.
>
> Are these issues due to the fact that I didn't run SWU_OBUF after the
> transports went in? Should SWU_OBUF be on our action log when modified
> workflows go into production?
>
> ---
> Carolyn Fuller
> Massachusetts Institute of Technology
> Information Services and Technology
> Administrative Computing
> Senior Analyst/ Programmer
> (617) 253-6213
> http://fuller.mit.edu/
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug


---
Carolyn Fuller
Massachusetts Institute of Technology
Information Services and Technology
Administrative Computing
Senior Analyst/ Programmer
(617) 253-6213
http://fuller.mit.edu/

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug