Hi Joe, I too have seen this issue where it works in the MT but not in WUT (post from 4/7/08 subject "Set an editable check box in a table field"). We found that WUT 7.0.01 with patches 5 & 6 had this issue while 6.0.1 patch 1321 and 7.1 did not. We never had any issue on the MT.
I have not been using WUT 7.5 much because it has issue with hanging on my 64-bit 2008/Win7 machines (7.1 does much better). I just fired up 7.5 p4 and tried the table/checkbox loop where we had this issue using 7.0.01 and the workflow worked as expected. Our workflow is a little different though. We do not evaluate $ROWSELECTED$, there is a button that checks all records and one that unchecks all records. Do you have any older WUT versions you can try it with? Jason On Fri, May 7, 2010 at 11:26 AM, Joe DeSouza <[email protected]> wrote: > ** > Fellow ARS geeks, > > Usually its not unusual to expect some things to work on the thick client > but not on the mid-tier due to obvious limitations with the web tier.. But > when its the other way around, I would just conclude it must be some sort of > a bug... > > I have a simple piece of work-flow that works quite well on the Mid-Tier > but when I try the same on the WUT, it doesn't work 100% correctly. > > The work-flow is on a table field where an active link guide runs through a > table on a form, and sets an editable check box on that table field to > checked if the row is selected, and unchecked it if the row is not selected > by evaluating the value of $ROWSELECTED$. > > This partially works on the thick client - it works on every entry on the > table field except for the first entry. On open of the form since that first > entry is always selected, the work-flow works, and does check the check > box.. > > However if another row is selected causing the first rows check box to be > unselected, and the you return the row selection to the first row, the check > box fails to get checked. For some reason it is as though the row is not > selected as the Active Link in the guide that evaluates $ROWSELECTED$ > evaluates it to 0 as if is not selected, thus failing the qualification and > not setting the check box.. > > This work-flow works on every other entry correctly. > > This works correctly on the mid-tier every which way you try it.. even on > the first entry on re-selecting it. > > My user client as well as the Development Studio client is at Patch 4 of > 7.5. The server and the mid tier are at patch 3 0f 7.5. I had upgraded the > Studio and the user client on the recommendations of Remedy Support to > resolve a few problems with Patch 3 of the User client.. > > Thanks for any response.. > > Cheers > > Joe > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
