Transport of Standard tasks

[BPT Consulting]

David,
 
Depends on what kind of changes you’re making to the tasks?   
 
Examples:
A change in WI or long text or method logic will not require a transport of the template.
 
If a container element is added/changed or the Business Object/method is change, you will have to modify the bindings within the Workflow.  This will require a transport of the template.
 
Once you make all you changes in DEV and test the functionality out, the transport(s) will be your final answer.  By the way, you do not have to create a new version in DEV.  Workflow handles the version management.
 
Regards,
Thomas Maue

--- On Mon, 2/22/10, david.s.dittmer at accenture.com <david.s.dittmer at accenture.com> wrote:


From: david.s.dittmer at accenture.com <david.s.dittmer at accenture.com>
Subject: Transport of Standard tasks
To: sap-wug at mit.edu
Date: Monday, February 22, 2010, 12:14 PM








Hello workflow experts,
I have developed a workflow template with a large number of standard tasks and transport the lot to QA. I now want to make changes to some of tasks. Please advise if I can just transport the changed tasks to QA or do I have to transport a new version of the template again. The changed tasks have not changed the flow of the workflow template.
  
Thanks 
David S Dittmer 
Accenture 
  
  
  
  


This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
-----Inline Attachment Follows-----


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100222/eaff731e/attachment.htm