WF not restartable after rule failure!

[Mat Yie]

It happened to me as well.
What I did was just to create a dummy step at the beginning of the
workflow. That would solve it.
Cheers.
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Michael Pokraka
Sent: Friday, February 06, 2004 7:58 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: WF not restartable after rule failure!
 
Hi Jocelyn,
Good point, tried it but it's not available - grayed out for some
reason. It
doesn't appear in SWI2_ADM1 either.
I think it may not work though because there is no WI which has rules to
evaluate at this point, only a top level workflow item exists.
 
Thanks (oh, also for the input on notifications),
Mike
 
Dart, Jocelyn wrote:
> Hi Michael/Paul, Did you try using the transaction SWIA option to
re-evaluate
> the rules?
> Jocelyn
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Bakker,
> Paul
> Sent: Tuesday,3 February 2004 8:49 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: WF not restartable after rule failure!
>
>
> Hi Michael,
>
>   I saw that exact same message on a recent workflow course. It
>
> even perplexed the instructor....!
>
> He discovered later that you cannot restart a workflow in which agent
>
> determination fails on the *first* step. This is because no WorkItem
>
> is created and therefore no data is held in the database tables.
>
>
> I suppose you just need to start a new workflow instance.
>
> regards
> Paul (who's glad to finally contribute an answer to WUG!)
>
>> -----Original Message-----
>>> From: Michael Pokraka [mailto:workflow at quirky.me.uk]
>
>> Sent: Tuesday, 3 February 2004 01:39
>> To: SAP-WUG at MITVMA.MIT.EDU
>> Subject: WF not restartable after rule failure!
>>
>
>>
>
>> Hi all,
>> I have a slightly nasty one (basis 6.20, 4.7 Enterprise):
>> A rule is set to 'terminate if no result' and fails. I can
>
>> fix the cause, but then cannot restart the workflow. If I try
>
>> restart it simply logs an error saying 'Workflow instance
>
>> data not in database', the long text of which contains scary
>
>> terminology like 'serious inconsistency in the database'...
>>
>
>> I'm logging this with OSS as well, but would be interested to
>
>> know if anyone on the list has bumped into this one.
>>
>
>> Cheers
>> Mike
>>
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
intended
> solely for the use of the individual or entity to whom they are
addressed. If
> you have received this email in error please notify the system manager
of QR.
>
> This message has been scanned for the presence of computer viruses. No
> warranty is given that this message upon its receipt is
> virus free and no liability is accepted by the sender in this respect.
>
> This email is a message only; does not constitute advice and should
not be
> relied upon as such.
> **********************************************************************
>
>