Container and DB modification simultaneously

[Ulrich Mende]

Hi, Arpad
Can I suppose that
 - "write to the database" means asynchron database update (in update
task)
 - "modify the container" means having a return value or/and export
    parameters in the method?
 
Every task, calling an asynchronous method must have at least one
terminating event.
This event usually is triggerd by the application and returns all
interesting values back to the teask via the event container. In the
task definition you have a binding from that event container to the task
container. This binding substitutes the direct data flow between method
container and task container in a synchronous method. If you need the
results of the task  in the workflow container too (to controll the
workflow), use the additional binding between task and workflow.
 
The workflow will allways wait for that terminating event of a task. So
from the workflows point of view every task is synchronous, what means
that at the end of the task the result of the called method can be used.
So if you want to model the different return valus of a asysynchronous
task in the workflow, insert a case-statement in the workflow just after
the task.
A special background step will be necessary only when the information
transferred by the terminating event is too less and you want to read
additional data from the database ...
 
On the other hand you are free to make direct database updates (insert,
modify, update) in a synchronous task as well.
 
Best regards Uli
 
 
 
Vincze Arpad <Arpad.Vincze at itelligence.hu> schrieb am 18.03.2002,
11:12:40:
> Hello,
>
>
>         I have a workflow  "task", which would like to write the database
> (using the call transaction mechanism),
>          and it wants to modify the container also.
>
>         As far as I know an asynchronous task can modify the database, but
> it should not modify the container,
>         and inversely a synchronous task can modify the container but should
> not modify the database.
>
>
> So my proposed solution:
>
>   Asynchronous dialog task
>     [Containing the DB modification: the SAP call transaction]
>   Event output 1
>  Background synchronous task
>     [Containing the workflow container modification]
>
> This method (sequence) is acceptable, but not so nice ...
>
> Is there any better solution, with better performance?
>
> Regards:
>        Arpad
>
> Vincze Arpad
> itelligence Hungary Kft.
> H-1138 Budapest, Vaci zt 141
> Tel.:   (+36 1) 452 3822
> Fax:    (+36 1) 452 3839
> Mobil:   (+36 20) 9 533 578
> arpad.vincze at itelligence.hu