Advise and question about adding container elements for monit oring purposes

[Soady, Phil]

Hi Fred
Out of interest Why didn't you want someone to re-use the tasks ?
Which problems are these?
 
Re-use of tasks is one of the goals, so im interested why
someone deliberately tries to avoid re-use.
 
Regards
 
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
 
-----Original Message-----
From: Kouw, FA - SPLTX [mailto:fa.kouw at td.klm.com]
Sent: Tuesday, July 29, 2003 10:21 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Advise and question about adding container elements for monitoring purposes
 
 
Thanks Mike !
 
I was referring to note 125400, but didn't understand the impact of changing the container. Now (I think) I do. I'll add the container element and add the binding from the triggering event to that container element.
 
In my case copying my workflow also means copying the tasks (and replacing the tasks and (re)defining the bindings), because I created tempate specific tasks (included the template ID, the last 3 numbers in the task abbreviation). I've done this to be sure that tasks are not re-used, in order to prevent problems that can occur when using tasks in different workflows. Maybe this was not a very smart thing to do...(?)
 
Regards,
 
Fred
 
Michael Pokraka wrote:
 
> Hi Fred,
> Not sure if these are your guidelines, but have a look at Note 125400.
>
> Your scenario makes perfect sense. As a general rule of thumb, adding
> container elements is fairly safe, but changing or deleting them can
> be deadly. Also, copying a workflow is not a lot of work - you are
> only copying the definitions contained in the WS... template. The
> tasks remain the same. The only other thing that may need additional
> work is fi you e.g. delete a container element. You would need to
> remove any bindings from tasks that you use in your new flow. HTH
> Cheers Mike
>
> On Tue, Jul 29, 2003 at 11:49:54AM +0200, Kouw, FA - SPLTX wrote:
> > Hi,
> >
> > One thing I found out after going live:
> >
> >    * for monitoring purposes it is advisable to include related business
> >      objects in the workflow container.
> >
> > F.i. a workflow that is started by/for an incoming Idoc: in my case
> > the Idoc contains a reference to a PO (and the Idoc business object
> > already has an attribute that refers to the PO object instance).
> > Only when I add a container element 'Purchase order' in the workflow
> > container (and fill it, f.i. using the binding from the event to the
> > workflow) then it's possible to select the workflow by referring to
> > the PO --> when using SWI6 you specifiy the PO, when using 'Services
> > for object' you display the PO and select this function. Otherwise
> > it is not possible to quickly select the 'Idoc workflows' that are
> > related to the PO!
> >
> > I have one question: do I need to create a new version of my
> > workflow, or even copy the whole workflow, when adding a container
> > element to the workflow container and and populate it using the
> > binding from the event to the workflow (I've read the guideliness on
> > this subject, but do not completelty understand if this is a
> > compatible or incompatible change)? Copying the workflow whould mean
> > a lot of work: I created many tasks specifically for this workflow
> > template (task abbreviation contains the workflow template ID, we
> > have chosen not to re-use tasks within different workflow
> > instances).
> >
> > Regards,
> >
> > Fred Kouw
> >
> >
> > ********************************************************************
> > **
> > This e-mail and any attachment may contain confidential and privileged
> > material intended for the addressee only. If you are not the addressee, you
> > are notified that no part of the e-mail or any attachment may be disclosed,
> > copied or distributed, and that any other action related to this e-mail or
> > attachment is strictly prohibited, and may be unlawful. If you have received
> > this e-mail by error, please notify the sender immediately by return e-mail,
> > and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
> > subsidiaries and/or its employees shall not be liable for the incorrect or
> > incomplete transmission of this e-mail or any attachments, nor responsible
> > for any delay in receipt.
> > **********************************************************************
> >
> > ____________________________________________________________________
> > _________________________
> > This outbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
> > For further information visit: http://www.veiliginternet.nl
> > _____________________________________________________________________________________________
>
> ______________________________________________________________________
> ___________________
> This inbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
> _____________________________________________________________________________________________
 
 
**********************************************************************
This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt.
**********************************************************************
 
_____________________________________________________________________________________________
This outbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs. For further information visit: http://www.veiliginternet.nl _____________________________________________________________________________________________