Task to WF binding failing for reject execution

Workflow Developer mysapwug at yahoo.com
Fri Aug 20 11:22:16 EDT 2004


Greetings,
We have upgraded our development system from 4.6c to 6.20 sp41. One of
our custom workflows goes into error status because a container element
is not set after reject execution of the dialog step (standard task)
TS...). The error is WL410 'Workitem could not be created'. We also get
the error 'Mandatory import element LASTAGENT has no value', which
causes the WL410 error.
 
The task has a binding from _WI_ACTUAL_AGENT of the task container to a
LASTAGENT element of the workflow container. The LASTAGENT element is
then used as actual agent for the next step, which is a subworkflow
that handles reject processing.
 
In examining the containers from the Workflow technical log, I can see
that the element _WI_ACTUAL_AGENT of the task has the correct value.
However the LASTAGENT element of the workflow container has initial
value, indicating that the runtime binding after task completion did
not take place.
 
This workflow has been productive in 4.6c for about two years, without
problems. Also checking the workflow and task shows no binding errors
or warnings.
 
Thanks in advance for any assistance you can offer.
 
Robin Sahasranam
Workflow Administrator/Developer
World Bank
 
 
 
---------------------------------
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
 


More information about the SAP-WUG mailing list