Background method causing problems

[vijay srikanth]

Hi Mark,

I am adding a 3 second delay in the check completion step.
How do I implement the other thing, that you're talking about 'The Work Item 
Condition' on the first step. How do I set such a condition. Isn't that 
exactly what the background check would be doing?


Regards,
Vijay


>From: Mark Pyc <mark.pyc at gmail.com>
>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>Subject: Re: Background method causing problems
>Date: Tue, 20 Dec 2005 09:49:26 +0000
>
>G'day Vijay,
>
>You could try a few different things.
>
>An oldy and not necessarily a goody is a 1 minute delay via the requested
>start option on your background check.
>
>Depending on your release you could consider using the 'complete work
>item condition' on the first step.
>
>Have fun,
>Mark
>
>
>On 12/20/05, vijay srikanth <vijay_d15 at hotmail.com> wrote:
> >
> > Hi,
> >
> > I am developing a workflow to ensure sales order completion. There is a
> > step
> > that takes the user to the sales order incompletion log. Then there is
> > background method to check if he has completed the sales order fully. If
> > he
> > does not complete it then the work item is recalled in his inbox. 
>However
> > if
> > he completes it, then the work item should not appear again. But the
> > background job I think occurs before the changes to the sales order is
> > committed. It again returns a container value saying that the sales 
>order
> > is
> > incomplete, even though It is not. How do I avoid this problem.
> >
> > Regards,
> > Vijay
> >
> >
> > _______________________________________________
> > 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