Security Error on DS Form for wfwk.3

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3288
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1348
Roger French	1311
mark.cook	1244

Woozy

Veteran Member

Posts: 709

7/20/2010 5:48 PM

I have created a series of Design Studio versions of WFWK.3 (workflow trigger). Basically, I modified the form to default the service name and description, and removed the fields that were not required.

All the forms work fine for me, but other users can see and use one of the forms, but get a Servlet Xpress error when they try to use the others (see attached).

The xml files are identical except for the defaulted fields.

The only other difference is security. I have full rights (under LAUA), and the other users have limited rights (under LS Security). The users can see and use WFWK.3 directly, and they can see and use one of the DS forms, but not the others.

Our security folks are out of ideas.

I have tried:
- reindexing forms
- changing prodline/changing back
- IOS Cache Refresh

I have attached 3 files: the error message received when selecting the bookmark, the DS form that works (wfwk3ltmint_supers.txt) and one of the DS forms that don't work (wfwk3ltmint_jobs.txt).

I'm stumped on this one, and I'd appreciate any help I can get. Thanks!

Attachments

John Henley

Senior Member

Posts: 3348

7/20/2010 6:32 PM

Are any of the other users using locales?
Have you tried checking file permissions on the .xml files?

Woozy

Veteran Member

Posts: 709

7/20/2010 6:39 PM

Yep - they are all lawson/lawson 0666.

John Henley

Senior Member

Posts: 3348

7/20/2010 6:47 PM

Are any of the other users using locales?

Woozy

Veteran Member

Posts: 709

7/20/2010 6:52 PM

Nope - we don't have any locale options other than default.

Woozy

Veteran Member

Posts: 709

7/20/2010 7:03 PM

By the way, I also had the user try using my machine/browser, where I know the forms all work for my user. He got the same error on my machine as he did on his own machines.

John Henley

Senior Member

Posts: 3348

7/20/2010 7:36 PM

Did you modify the DS .xml by hand?
Reason I ask is because in the file that doesn't work, on the _f3 / SERVICE field, you have an attribute deftkn="" and you don't have that in the .xml file that does work...

Woozy

Veteran Member

Posts: 709

7/20/2010 8:08 PM

I didn't modify any of the files by hand.

Woozy

Veteran Member

Posts: 709

7/22/2010 6:41 PM

Well, I finally got to the bottom of it. It appears to me this is a little bug in Design Studio.

John nailed it when he mentioned the deftkn attribute that was in the non-working file and not in the working file.

It appears that when a field is changed to "output only" using Design Studio, one attribute is changed (tp="Text" becomes tp="Out") and four new attributes are added (hsel="0" hdet="0" hselrul="0" deftkn="") to that field in the xml file.

It appears that the deftkn="" is causing the problem. If I change it to deftkn="0", then the problem goes away immediately.

For even more fun, if the "output only" setting is removed, the deftkn=0 attribute is not removed so the error remains.

LAUA security isn't bothered by this attribute, but LS Security takes a big nose-dive when it sees it.

By the way, we're on DS v9.0.1.4.199.

Off to create a CASE ticket...Yay.