Passing the agent to the container element

[Carolyn Fuller]

Mike,
 
It is 4.6 but it does not involve deadlines. We've narrowed down the
problem a bit more. We've been able to reproduce it in our
development environment. It is an asynchronous method. If the task is
executed from the in-box it seems to populate the workflow container
correctly, otherwise it does not.
 
Am I correct that the only data an asynchronous task can pass to the
workflow container is data passed to the task from the terminating
event?
 
Carolyn
 
>What version, and do they involve deadlines?
>If the answers are 4.6 and yes, I've a similar problem which has
>been with OSS for over a month already: When a deadline expires, it
>sometimes (!) evaluates the return bindings - but since there was no
>execution this results in blank or incorrect values.
>I can give you more details if it applies to you.
>
>Cheers
>Mike
>
>On Tue, Jun 03, 2003 at 06:26:20PM -0400, Carolyn Fuller wrote:
>>  Hi all,
>>
>>  A year ago, Jocelyn Dart recommended the following steps for passing
>>  the actual agent from a task to the workflow container, so that a
>>  subsequent step can pick it up:
>>
>>  1. Create a workflow container element, e.g. LASTAGENT, based on
>>  database field WFSYST-AGENT.
>>  2. In the first step, in the Task -> Workflow section of the binding, use
>>  the SHOW LINES button to see all possible elements of the task.  Bind
>>  the "Actual Agent" (also appears as "Actually Processed by" depending on
>>  version) to your workflow container element LASTAGENT.
>>  3. In the following step, in the agent assignment use the EXPRESSION option
>>  to assign LASTAGENT as the agent for the second step.
>>
>>  ==========
>>
>>  We are doing this in one of our workflow templates and it was working
>>  well until recently, when the template was modified and transported
>>  to production. The modification to the template did not involve
>>  either of the two steps that are passing/receiving the agent. These
>>  steps are working in our development environment.
>>
>>  When I look at the contents of SWIWIOBJCT-WI_AAGENT for the step that
>>  should be passing the agent, it is empty for the problem workflows.
>>  This field was consistently filled in properly before and it is still
>>  filled in properly in our development environment.
>>
>>  What could be wrong?
>>
>>  Thanks,
>>
>  > Carolyn
 
 
--
 
Carolyn Fuller                               M.I.T.
fuller at mit.edu                       Financial Systems Services
Senior Analyst/ Programmer Peer Leader      W92-210
fax (617) 253-9661                    voice (617) 253-6213
http://fuller.mit.edu/