Re: [ebxml-bp] Episodical memory requirement

["David RR Webber" <david@drrw.info>]

Anders,

I believe this is the purpose of the JOIN.

To prevent something completing before all necessary 
prior steps have completed.

See the JPG of the model and activity flow here - that 
implements exactly the example you provide (I believe).

 http://drrw.net/visualscripts/#ebxml 

Thanks, DW.

----- Original Message ----- 
From: "Anders W. Tell" <anderst@toolsmiths.se>
To: <ebxml-bp@lists.oasis-open.org>
Sent: Tuesday, June 08, 2004 3:31 AM
Subject: [ebxml-bp] Episodical memory requirement


> Dear Team
> 
> I was asked to provide a use case that show the need for Memory in 
> ebBP,ie. requirements for keeping information between exchanges of data 
> messages.
> 
> Use case:
> 3 transactions are defined in an ebBP or BPSS: Order{PO}, 
> OrderAcceptance{POC}, RequestForPayment{Invoice}.
> 
> Two partners enact two business-dialogs in parallell
> BD1:  PO1 with goods for 1M Euro -> Order is accepted with POC1
> BD2:  PO2 with goods for 100 Euro -> Order is accepted with POC2
> 
> In order to make sure that the Invoice sent in B.Dialog BD1 is in any 
> way is related to POrder1 something must be remembered about PO1 
> otherwise it is possible to send an invoice related to PO2 in the 
> B.Dialog1 and thus complete BD1 leaving BD2 behind.
> 
> hope this  helps
> Thanks
> /anders
> 
> -- 
> /////////////////////////////////////
> / Business Collaboration Toolsmiths /
> / website: <www.toolsmiths.se>      /
> / email: <anderst@toolsmiths.se>    /
> / phone:  +46 8 562 262 30          /
> / mobile: +46 70 546 66 03          /
> /////////////////////////////////////
> 
> 
> 
>