Keep Single step task from completing until Dead Line date

[Rick Sample]

Mike,
I am not in the ofc right now, but it was the first 
exception from the call to SWW_WI_START. 

Bottom line, if I have a terminating event in the task 
the task should not be set to completed until this event 
triggers event if I execute the task. Yes? 

When I call the SWW_WI_START, do I need to add or change any 
parms for this to wait for term event?

Before Async changes:
I start the task via SWW_WI_START. I use the Deadline date and action. 
This works fine. 
I have a method on zbus2032-doSomething. From this method, I call a 
program and return. Task gets set to Comppleted status. 
Also, if dead line is reached it gets set to completed. 
This is expected results.

After Async changes:
Start Task with SWW_WI_START with same Deadline date and action. 
Added a zDummy event to zbus2032. 
Added the event to the terminating events in the Task. 
Changed the method I call in zbus2032 to Async. 
Save / complie changes on bus2032 and my task.

The thinking here is that the task shouldn't be set to complete 
until the event triggers. 

The ESS Time Approval is a singel step task and waits for a 
term event to complete. I will look at it Monday and compare. 

Thanks!
Rick


>>> wug.replies at workflowconnections.com 01/19/06 17:01 PM >>>
Hi Rick,
That should definitively work. The method has to be asynchronous though,

it seems you had some other problem preventing it starting. Can you 
clarify "Failed to start"?

Cheers
Mike

Rick Sample wrote:
> I tried to start the Task with the object method set as asynchronous.
> Failed to start. 
> 
> I tried a zdummy terminating event in the Terminating Events. Didn't
> matter. 
> When I execute the task, it completes! 
> 
> I checked out the code in the Confirm to Complete FM. Way too much
work
> for a simple task. 
> Looks like the simplest way is to create a WF with the task and loop
> until terminating event or 
> deadline reached. 
> 
> Any other ideas, fire away...
> 
> 
> 
> 
>>>>David.Trant at andrew.com 1/19/2006 14:25:03 >>>
> 
> What about making it an asynchronous task and finding/creating a
> terminating event to shut it down when the deadline is reached?
> 
>  
> 
> ________________________________
> 
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> Behalf
> Of Edwin Mukusha
> Sent: Thursday, January 19, 2006 12:27 PM
> To: SAP Workflow Users' Group
> Subject: Re: Keep Single step task from completing until Dead Line
> date
> 
>  
> 
> 
> Hi Rick, 
> 
> I don't think you can do this without a workflow template of a writing
> this logic in a custom method (which would amount to the some effort
> anyway).  You are better off putting this standard task in a wf
> template
> where you will more options at your disposal. 
> 
> sorry if this is not answer you wanted. 
> 
> Edwin. 
> 
> 
> 
>  
> 
> "Rick Sample" <Rick.Sample at gbe.com> 
> Sent by: sap-wug-bounces at mit.edu 
> 
> 01/19/2006 10:14 AM 
> Please respond to "SAP Workflow Users' Group" 
> 
>         
>         To:        sap-wug at mit.edu 
>         cc:         
>         Subject:        Keep Single step task from completing until
> Dead
> Line date
> 
> 
> 
> 
> I have an standard task that has a Confirm on end. Started via 
> SWW_WI_START. (I know, I need to change to API but not today)
> This keeps the task in the inbox until the user completes or until the
> Dead Line 
> is reached and then terminates. 
> 
> Now, business does not like the Confirm on End pop-up. (Don't ask!) 
> They want it to just stay in the inbox until the deadline date. The
> user could execute 
> the task several times and just not go away until dead line. 
> 
> I would rather not create a whole WF template just to loop. 
> Anyone know of a way to achieve this in 4.6c?
> 
> Rick
> 
> 
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu 
> http://mailman.mit.edu/mailman/listinfo/sap-wug 
> 
>
------------------------------------------------------------------------------------------------
> This message is for the designated recipient only and may
> contain privileged, proprietary, or otherwise private information.  
> If you have received it in error, please notify the sender
> immediately and delete the original.  Any unauthorized use of
> this email is prohibited.
>
------------------------------------------------------------------------------------------------
> [mf2]
> 
> _______________________________________________
> 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