Dynamic Parallel Processing with Modeled Deadline Monitoring

[Mike Pokraka]

Hi Paul,

Not sure I understand the problem: Do you expect only one deadline to be
hit? As I see it all parralel items should hit the deadline at the same
time. I am not sure in practice, but I'd expect them all to have their own
'obsolete' branch. Having only one obsolete branch also makes sense,
depending on point of view (may be worthwhile clarifying with OSS what the
designed behaviour is supposed to do).

Another way to model that type of setup is to have your processing in one
side of a 1of2 fork, and in the other branch you put a wait step (dummy
method with no code) with a requested start followed by your deadline
handling.

Cheers,
Mike


On Tue, January 12, 2010 2:57 am, Paul Borriello wrote:
> Hi All:
>
> I have a requirement to perform an ECN Decision Step, with Dynamic
> Parallel
> processing, for 4 approvers, including Modeled Deadline Monitoring.  The
> Dynamic Parallel Processing works fine.  My issue is with the Modeled
> Deadline Monitoring.  When the deadline hits, I set the Approval Workitem
> to
> Obsolete via Process Control.  For one of the Approvers, it sends out the
> Deadline Email and then ends the WF for all of the Approval Workitems,
> even
> if they are not in Deadline.  If I do not set the Workitem to Obsolete,
> the
> Deadline Approval Workitem will not loop back to the Approver Inbox until
> the other three Approval Processes have completed.
>
> When I remove the Dynamic Parallel processing the Deadline Monitoring
> process works fine.
>
> Any thoughts or ideas on how to remedy this situation?
>
> Thanks in advance for you responses.
>
> Regards,
> Paul
>
> Paul Borriello
> PAB Consulting, LLC
> 973-635-3412-office
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>