Advise and question about adding container elements for monitoring purposes

[Kouw, FA - SPLTX]

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
_____________________________________________________________________________________________