EBP WF - Standard task triggered when template was not

[Dart, Jocelyn]

Hi Meagan,
Unless you have added triggering events to the standard tasks it's
difficult to see how the situation you describe could have occurred.
Are you sure no-one has run the workitem deletion programs at all?
Of course these should not be run in production - archiving object
WORKITEM should be used even in an EBP system.
 
The start conditions aren't relevant unless you have added triggering
events to your tasks, i.e. they are only relelvant if you have an
actual event linkage.  You should not have triggering events on your
standard tasks, only at the workflow level.
 
If you have delegated BUS2121 to your own object and added attributes
there can be problems with start conditions particularly if your
attribute is coded to return an exception (which will cause the start
condition to fail) or if it returns an incorrect value for a simulated
shopping cart (i.e. during approval preview).  However, again, start
conditions are only relevant to event linkages.
 
The shopping cart programs effectively evaluate the event linkages
at runtime, checks that one and only one workflow is found
and then starts the workflow found directly.  Putting the event
linkage back in the log is not helpful in a production environment
as of course running the event log all the time can significantly
degrade performance.
 
There is a program Z_CART_LINKS in OSS note 329564  that will help you find
the relevant
standard tasks attached to your object.  You should then use the work item
display GOTO > WORKFLOW LOG option to go to the matching workflow log.
 
It might also help to get in some workflow expert help, e.g. from SAP
itself,
to go over your workflow administration procedures and check you have
workflow set up in your production system correctly.
 
Regards,
        Jocelyn Dart
Consultant (EBP, BBP, Ecommerce, Internet Transaction Server, Workflow)
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
 
 
-----Original Message-----
From: Van Heerde, Arnoud
Sent: Tuesday, 5 February 2002 2:00 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: EBP WF - Standard task triggered when template was not
 
 
Hi Meagan,
 
>From my experience with EBP 2.0 I found that start conditions can be a
problem. You say you checked event linkages and bindings, but it maybe a
good idea to check the start conditions too. Are there start conditions for
the tasks? If you check the event log (SWEL) you probably cannot find the
event coveragereq.saved in there. That is because the workflows are started
"directly" from the application. Maybe that is why it looks like the
workflow template was not triggered. In my case I created an additional
virtual attribute for the coverage request called "WorkflowToBeStarted". The
start condition was then reduced to checking this attribute and starting the
corresponding workflow. Furthermore I made sure that all other (coverage
req. related) event linkages are turned off. After you activate the start
condition you can be sure which workflow is started (an entry in the event
linkage table will be created after activation and you can also see the
check function module that implements the evaluation of the start
condition). Another thing is the JavaApplet used for displaying a preview/
history. It may not display your custom template correctly and could give
you the impression that certain critical steps were not performed. There are
notes to fix that problem and you can download a new applet from SAPSERVx.
 
HTH
 
Arnoud
 
-----Original Message-----
From: Meagan Tesdall [mailto:meagan.tesdall at us.pwcglobal.com]
Sent: Tuesday, February 05, 2002 12:49 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: EBP WF - Standard task triggered when template was not
 
 
Hello all,
 
A few weeks ago, I had submitted a question about WF logs and that I could
not find a log for certain workflows that had routed incorrectly. We have
since discovered that the standard tasks which are part of our workflow
template have been triggered but the template itself was not tirggered so
many critical steps are not performed.
 
We have verified all event linkages and bindings. We are working in EBP v
2.0 with an R/3 backend (4.6). The workflow is performed only in EBP. The
problem is not consistent or repeatable, occurs only in our Production
environment; it has happened to 8 shopping carts (that I know of) out of
just over 3000.
 
Please help!
thanks in advance!
Meagan Tesdall
----------------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.