Serouche, I experienced a similar problem about a year ago. I did development on my laptop running AR System 6.3 patch 18(19?). Everything worked fine. I migrated the workflow to a test system (on AIX) running AR System 6.0.1 patch 13(?). I had all kinds of problems. I suggested upgrading the test AR System server to 6.3 latest patch. After doing so the problems went away.
If upgrading your AR System server to 6.3 is at all possible, I would recommend that. Roger Medsker Remedy Consultant Bluestem Consulting Group, LLC [EMAIL PROTECTED] -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Peter Romain Sent: Monday, December 03, 2007 9:24 AM To: [email protected] Subject: Re: there must be a way to do this ... please read and help ... Hi again Serouche, I spent a fair amount of time helping you with this. You will remember that it worked for me on V6.3 and V7.01 so there is nothing fundamentally wrong with what you are trying to do. I suggest that you create a couple of new forms just to test this scenario without all of the additional processing your current workflow does. When you've done this you could send me the def and I can try it on V6.3 and V7 systems without having to change the workflow at all. I suspect that it's the V6.1 system that has a bug stopping this working. Cheers Peter > Dear listers, > > I already posted this issue few times during the past month. Without any > success. > And i am still stuck. > What I try to do is to loop on a table. But it doesn't behave > correctly. My concern is that I am not sure whether it is related to the > workflow I wrote or if it is a limitation of the ARSystem we are > running, v6.01 with latest patch > This is what I do: > on the web I fill in a character field with several logins. I push a > button which sends the lines to a form A. > On Submit on that form I fire a filter guide. > The filter guide takes each login and checks whether it is in the User > form. If no, it checks whether the entry exist in Form B AND whether it > corresponds to a "list name". > This Form B contains a list of distribution lists with "list name" and > "member name". > If the "list name" = the login checked, a tempfield takes this value. On > Form A I have a table field with a qualification as follows : tempfield > = list name > So if "list name" = the login checked, is met then the table takes the > list name and I am able to read into a loop the values of members found > in the table. > Everything works fine, except that if I put 2 tables, the workflow > returns back two times the same members of the first list found. > > Is anybody able to help with this problem? > Thank you. > > Serouche > > ____________________________________________________________________________ ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
