modelled Deadline R3 4.7

[Mark Pyc]

The dummy method is simply an empty method that does nothing. You could add
it to the main object you're working with or maybe create a special object
to keep it separate. The method would have no parameters or exceptions. You
can mark it as Instance Independant so you don't even need to pass it an
object reference.

It's a bodge, but it works.

Have fun,
Mark


On 7/26/06, John A Haworth <jhoworth at csc.com> wrote:
>
>
> Thanks
>
> I like the Requested Start on a one of the branches of a fork, What kind
> of dummy task could i use though.
>
> Cheers
>
> JOhn
>
>
>
> ----------------------------------------------------------------------------------------
>
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery. NOTE: Regardless of content, this e-mail shall not operate to bind
> CSC to any order or other contract unless pursuant to explicit written
> agreement or government initiative expressly permitting the use of e-mail
> for such purpose.
>
> ----------------------------------------------------------------------------------------
>
>
>
>   *"Mark Pyc" <mark.pyc
> @gmail.com>*
> Sent by: sap-wug-bounces
>
> 26/07/2006 13:54
> Please respond to "SAP Workflow Users' Group"
>
>         To:        "SAP Workflow Users' Group" <sap-wug at mit.edu>
>         cc:
>         Subject:        Re: modelled Deadline R3 4.7
>
>
>
>
> G'day John,
>
> The Decision has been made, so the deadline isn't valid.
>
> If you want a deadline over the whole process resulting from the decision
> you need something different. You could use a 1 from 2 parallel branch and
> in the other branch include a dummy step with a Requested Start (delay
> deadline), so that if the whole decision branch isn't complete in time the
> dummy step will run, do nothing and then allow you react at that point, or
> shut down the parallel branches and do whatever.
>
> Or you could put the decision and therefore it's branches in a subflow and
> use a deadline on the subflow step.
>
> Or....
>
> Have fun,
> Mark
>
>
> On 7/26/06, *John A Haworth* <*jhoworth at csc.com* <jhoworth at csc.com>>
> wrote:
>
> Hi everyone
>
> I have a 'latest end' modelled deadline on a decision task. One of the
> decisions takes the user to a sub workflow.
>
> My question is that, if i do not execute the decision task, the deadline
> kicks in ok. If I execute the decision task and choose the leg that takes me
> to the sub workflow, but dont complete the sub workflow activity, I want the
> deadline to still operate, but it doesnt, I am obviously missing something,
> anyone advise what?
>
> Kind Regards
>
> John
>
>
>
> ----------------------------------------------------------------------------------------
>
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery. NOTE: Regardless of content, this e-mail shall not operate to bind
> CSC to any order or other contract unless pursuant to explicit written
> agreement or government initiative expressly permitting the use of e-mail
> for such purpose.
>
> ----------------------------------------------------------------------------------------
>
> _______________________________________________
> SAP-WUG mailing list*
> **SAP-WUG at mit.edu* <SAP-WUG at mit.edu>*
> **http://mailman.mit.edu/mailman/listinfo/sap-wug*<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
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060726/3c8f0755/attachment.htm