<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2800.1479" name=GENERATOR></HEAD>
<BODY id=role_body style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: Arial"
bottomMargin=7 leftMargin=7 topMargin=7 rightMargin=7><FONT id=role_document
face=Arial color=#000000 size=2>
<DIV>
<DIV>
<DIV>Yes Mike, went through all those about two and half years ago right after
our upgrade. All the things you mentioned as well as container elements suddenly
disappearing and causing binding errors. LIke you said, because of the tight
schedules I did not really pursue it with OSS. What I did in some extreme cases
was to rebuild the WF step mby step from scratch. Some of these errors seem to
have gone away after applying some support packs.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>
<DIV><FONT lang=0 face=Arial size=2 FAMILY="SANSSERIF"
PTSIZE="10">Regards,<BR>Ramki Maley<BR>Workflow Developer,
USCBP.<BR>248-613-1287 (C)</FONT></DIV>
<DIV> </DIV></DIV>
<DIV>In a message dated 6/29/2005 1:49:15 PM Eastern Standard Time,
wug.replies@workflowconnections.com writes:</DIV>
<BLOCKQUOTE style="PADDING-LEFT: 0px; MARGIN-LEFT: 0px"><FONT
style="BACKGROUND-COLOR: transparent" face=Arial color=#000000
size=2>Greetings folks,<BR><BR>Is anyone else finding the WF builder on 6.20
bl**dy unreliable? I'm<BR>logging the same/related problems with OSS for the
third time now, things<BR>like:<BR><BR>* Adding a while loop produces "Illegal
node-id in Nodevalue-Table" (and<BR>lets you continue building)<BR>*
Copy/paste: Some steps/blocks can no longer be copied, it either
gives<BR>message "Binding direction 123 with index". (I was very happy to find
a<BR>note 853498 that addresses this one, only to find out it just
'corrects'<BR>the error message to "Function not permitted on selected
node")<BR>* Random corruptions that reappear some time later - I have 'hidden'
steps<BR>in my navigation area that are no longer in my flow (deleted). Or I
delete<BR>something and it deletes the whole loop that it's in.<BR>I have a
strong suspicion that much of it is related somewhere....<BR><BR>The reason
I'm asking here is that I'd like to hear any techniques or<BR>experiences
others may have had. Have you dealt with OSS on this one? Any<BR>useful
feedback? I've had a note which fixed it at one client and now at<BR>another
I'm encountering the same problems even though the note
is<BR>applied.<BR><BR>The problem with reporting these things to OSS is the
usual consultants<BR>dilemma: Whilst OSS may be very helpful, my client will
not sponsor the<BR>time for me to sort this out. More so the case on
short-term projects to<BR>implement one WF process in a very ambitious
timeframe.<BR><BR>Anyway.. enough ranting, any input of similar experiences
would be<BR>appreciated,<BR>Cheers<BR>Mike Pokraka<BR>Senior
Consultant<BR>Workflow Connections Ltd.<BR>Mobile: +44 (0)7786 910
855<BR>_______________________________________________<BR>SAP-WUG mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV></DIV>
<DIV> </DIV></FONT></BODY></HTML>