General design question to prep for 4.6c -> ECC6

[Sample, Rick]

Sorry Mike, 
Branches, nodes, forks, knives,...

Got it!

Rick




-----Original Message-----
From: Sample, Rick 
Sent: Thursday, August 02, 2007 8:50 AM
To: 'SAP Workflow Users' Group'
Subject: RE: General design question to prep for 4.6c -> ECC6

Hey Mike,

Got a quick question. You say 5 nodes. 
I have the Latest End DL, Approved, and Rejected branches off the
decision task. This is three. This appears to work.

Just wondering if I miss something?

Thanks,
Rick


 

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: Wednesday, August 01, 2007 11:01 AM
To: SAP Workflow Users' Group
Subject: Re: General design question to prep for 4.6c -> ECC6

5 nodes, no fork:
Use a modelled deadline and put a copy of your BG step in the deadline
branch and set a flag (do NOT set the approval to obsolete). In the
approval outcome, check the flag and if not set then execute your BG
step.
Cheers,
Mike

On Wed, August 1, 2007 4:11 pm, Sample, Rick wrote:
> I have to create a new WF in 4.6c. We will be moving to ECC6 on our 
> business side of house next year. Right now, I have the luxury of 
> having
>
> ECC6 in HR sandbox, so I can play around with design in both versions.
>
> I have a block of logic that can be easily solved in ECC6 but not so 
> easy in 4.6c.
>
> Basic logic: (Keeping details to limit) In 2 leg fork.
>
> I need to have a background task that will need to wait X time before 
> executing OR when 2nd foreground task fork is Approved.
> When time = X OR 2nd task in other fork is Approved, execute and 
> complete background task and logic block.
> The background task can complete, but block must not complete until 
> agent has approved foreground task.
> i.e. 2 leg fork requiring both forks to complete.
>
> In ECC6, I can easily accomplish this with the new Conditions Tab on 
> task.
> This is the enhanced Deadline Monitoring and works BEAUTIFULLY!
> We can now start/complete tasks based on more than just Date/Time and 
> if conditions are not met, the deadline monitor re-evaluates every
run.
>
> In 4.6c, this is a tad more complicated. What I have so far is this:
>
> 2 leg fork,
> 1st fork (for background task) is split with another 2 leg fork
branch.
> sub fork 1 is just a task with a  Request Start time sub fork 2 is a 
> Wait for Approved Event listener.
> Either one will complete fork!
>
> 2nd fork (for Foreground Decision task). When Approved, complete task 
> and Raise Approved Event for my object. Thus, completing the 
> background fork.
>
> This works fine, but anyone have a more elegant alternate solution for

> 4.6c?
>
> I know this is a lot, so if clarification is needed, by all means ask.
> This is a design competition. Best solution gets 20 points... ;-]
>
> Rick Sample
> SAP Business Workflow Developer
> Graybar, Inc.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>


--
Mike Pokraka
Senior Consultant
Workflow Connections
Mobile: +44(0)7786 910855

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug