Determine if another event was simultaneously raised for same object?

[Dart, Jocelyn]

Hi, Also just remember you can't guarantee event order. Nothing wrong with your current approach IMHO. Jocelyn

Sent from my iPhone with many apologies for the spelling, grammar and any other deficiencies 

On 21/02/2012, at 6:49 PM, "Rick Bakker" <rbakker at gmail.com> wrote:

> Hello,
> 
> If I understand correctly, you have events X, Y and Z.
> 
> You want X to start off a workflow W1 and have it do ActionA,
> and then also do ActionB but only if Y or Z have not occurred.
> 
> One way to do this would be to have Y and Z both listed as triggering
> events for another workflow, W2, which does nothing but start and stop.
> 
> Then, W1 can test for the presence of W2 to know if Y and/or Z have occurred
> and whether ActionB then needs to be done.
> 
> Of course, W1 can only look at the past, not the future, so timing may be
> an issue. I assume all the events have the same object key.
> 
> --
> You could also cheat and look in the event table but that is not
> recommended - the event trace could be turned off at any time.
> 
> regards
> Rick Bakker
> hanabi technology
> 
> On Tue, Feb 21, 2012 at 8:42 AM, Hilsbos, Margaret A
> <Margaret.Hilsbos at dayzim.com> wrote:
>> Hi workflow experts,
>> 
>> 
>> 
>> I have an interesting problem that probably has a simple answer, but it’s
>> not coming to me, so I’m hoping someone can help.
>> 
>> 
>> 
>> For our custom purchase requisition workflow (BUS2105), we want to handle a
>> new custom event that is raised when a certain custom field is changed.  If
>> only our new event is raised, we want it to do two things – let’s call them
>> ActionA and ActionB.  But, if the SignificantlyChanged event and/or
>> ReleaseStepCreated is also raised (according to normal SAP logic and
>> customizing settings), then we want the result of our custom event to only
>> be ActionA. So, when our custom event is raised, I think it needs to know
>> what other events were also raised for the same object and the same save
>> action.
>> 
>> 
>> 
>> What would be the best way to determine whether other events were raised?
>>  Or is there a different way to look at this problem altogether?
>> 
>> 
>> 
>> Further info:
>> 
>> 
>> 
>> ·         We’re using change document BANF to raise the custom event, with
>> field restrictions limiting it to changes in our custom field. The custom
>> event is defined on a delegated subtype of BUS2105.
>> 
>> ·         The existing workflow definition listens for SignificantlyChanged
>> and cancels the current workflow, because a new workflow will be started on
>> ReleaseStepCreated.  I expect to add our custom event here and/or trigger a
>> separate workflow to handle the additional processing.
>> 
>> 
>> 
>> Thanks for any suggestions!
>> 
>> 
>> 
>> Margaret Hilsbos
>> 
>> Senior Business Systems Analyst
>> 
>> Corporate IT, Day & Zimmermann
>> 
>> 
>> 
>> 
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>> 
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug