Workflow version
Alon Raskin
araskin at 3i-consulting.com
Thu Nov 17 09:42:24 EST 2005
Well my experience with versioning has been less then pleasant (to say the least). As a general rule I avoid creating versions in the development system. I know that new versions are created in the target system if there is a run time instance of your WF. Versioning can be so complex because workflow is one of those things that has code as well configuration. To make it worse some of this 'config' is client depending while some of it is client independent......
I am pretty sure there is a SAP note out there that actually recommends making copies of your workflow in Dev before transporting any significant changes. The note has more details.....
Alon Raskin
e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com>
w: http://www.3i-consulting.com
________________________________
From: sap-wug-bounces at mit.edu on behalf of koenraad.janssens at arcelor.com
Sent: Thu 11/17/2005 07:58
To: sap-wug at mit.edu
Subject: Re: Workflow version
As far as I know you can't. It is however assumed good practice to use the function "create new version" whenever you make a new development cycle of a certain workflow on your dev system. If you would have done that from the start you could have had your dev - testing systems on sync... offcourse when going to production that would again be async.
If the system wouldn't create new versions with every new transported versions.. current running versions might (probably) go into error.
This might not be an issue on your development and testing (acceptance) system.... but just imagine what might happen on production systems.....
Met vriendelijke groeten,
Salutations,
Best regards,
Mit freundlichen Grüssen,
Atentos saludos,
Koenraad Janssens
Sidmar N.V. - ISM
Leverage Team - Programmer
Tel: +32 9 347 35 76
email: koenraad.janssens at arcelor.com <mailto:koenraad.Janssens at arcelor.com>
shrikant.golsangi at wipro.com
Sent by: sap-wug-bounces at mit.edu
17/11/2005 13:48
Please respond to sap-wug
To: sap-wug at mit.edu
cc:
Subject: Workflow version
Hi
We have a problem with the Workflow Versions in the Development and
Testing Environments.
When the Initial WF Development (Version:0000) is transported from the
Development to the Testing Environment, Version in both the Environments
are same. This is as expected.
Later changes are incorporated for the Same Workflow in the Development
Environment without changing the Version. When the changed Workflow is
released to the Testing Environment, Version of the Workflow changed to
0001. This is expected, as there are workflow instances running with the
previous version.
Given the number of test cycles and requirement changes, going ahead
there will be many versions generated in the Testing Environment. As
well the Version numbers in Development and Testing Client will not be
in Synch.
We don't want this and wish to overwrite the existing Workflow
definition with the latest changes. Could you please let us know what
should be done to stop generating versions in the testing Environment?
Regards.
Shrikant Golsangi
___________________________________________________________________________
EAS-SAP Practice
Wipro Technologies
Email: shrikant.golsangi at wipro.com <mailto:shrikant.golsangi at wipro.com>
www.wipro.com
___________________________________________________________________________
Confidentiality Notice
The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin at wipro.com immediately
and destroy all copies of this message and any attachments.
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
***********************************************************************************
This message should only be read by those persons to whom it is
addressed, and may contain confidential information, the disclosure
of which is prohibited. This message is not intended to create rights
or obligations without subsequent written confirmation of its contents.
If you have received this message in error, please notify us immediately
***********************************************************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 20517 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20051117/cc8174f0/attachment.bin
More information about the SAP-WUG
mailing list