EBP WF - Standard task triggered when template was not

[Van Heerde, Arnoud]

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.