LSF9 upgrade LAUA security - ALL Functions available, but page

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

Sherry Shimek

Advanced Member

Posts: 43

7/27/2009 8:08 PM

We are about to transition to lsf9 but have discovered a interesting form function issue. We are intending to use LAUA security until next year.

On GL90.1 and AC90.2, some of our security classes have ALL functions iindicated in LID for the form, but when the form is accessed in portal they do not have the pagedown option. They can only pagedown when the message in the lower left says More Records Exist - Use Page Down and hit inquire subsequent times. This gets to be a pain in long inquires where the user pages up and then had to get back to the More Records message to get to the data they are looking for. However on these same forms other security classes with ALL functions truly have all functions including page down.

Lacking page down on an inquiry screen is pretty annoying, but as we can't test all users we are concerned that there may be instances where users are missing crucial change functions and won't find them until go-live.

Any utilities programs that may clean this up or ideas on what is causing this issue?

Jimmy Chiu

Veteran Member

Posts: 641

7/28/2009 5:32 PM

does it occur in LID too?

MattD

Veteran Member

Posts: 94

7/28/2009 6:28 PM

It is located in the far right button with the drop down arrow. It initially says inquire but can be changed to say Page Down. These drop down buttons are new in LSF9 and can sometimes be confusing, especially in situations like this one.

Hope this helps.

Thanks.
Matthew

Sherry Shimek

Advanced Member

Posts: 43

7/28/2009 6:45 PM

Thanks Matthew. Unfortunately, the page down option doesn't exist in the drop down menu on the forms for some users. We have confirmed in form security that the users in question should have ALL functions on these forms. Page up is present, but Page down isn't. This makes scrolling rather awkward.

If More pages exist - Page Down is in the message bar, we can "page down" using Inquire. However if the user needs to zero in on an item by paging up and then back down, they can't. I don't want to explain this to our many finance users on such critical inquires as GL90.1, GL45.1 and AC90.2

Sherry Shimek

Advanced Member

Posts: 43

7/28/2009 7:20 PM

After loggin into LID, I was able to use my pagedown key on the keyboard to see all the data. There was however no pagedown key for my security class. Neither were they available for GL45.1 and AC90.2.

There is a page up key, but no page down.

Jimmy Chiu

Veteran Member

Posts: 641

7/29/2009 4:01 PM

Sherry,

go to your "productline\map\default" delete the xml/trm/hlp files for GL45/GL45.1/GL45.2/AC90.1 to AC90.9

Recompile GL45 and AC90

see if that would fix the issue.

Sherry Shimek

Advanced Member

Posts: 43

7/30/2009 8:56 PM

The recompile didn't work in the test environment. We often correct security glitches with that in our current version.

We have entered a ticket with Lawson, but are hoping to resolve this whatever way is faster.

mark.cook

Veteran Member

Posts: 444

7/31/2009 5:46 PM

Is this happening on just the Finance Forms. We had an issue on HR user fields that we could not page down, there was a patch to address it. It has been a while so I can't remember if it was an app patch or portal patch.

Sherry Shimek

Advanced Member

Posts: 43

8/3/2009 4:07 PM

Thanks, Mark. Yes, so far we have only found GL and AC forms that are affected. No patches have been discovered on the Lawson website or in Problem Tracker log.

LIS ticket in progress, but we go live 8/15 and need to resolve this quickly.

Sherry Shimek

Advanced Member

Posts: 43

8/6/2009 2:10 PM

Thank you everyone who responded. After closer investigation our security team realized that when they copied our current PROD security and copied the form security into the new LSF environment they didn't have a good copy. This resulted in some functions not transferring correctly. Another copy was made with more diligence and now security is working correctly. Security is working to compare security current production to the new LSF9 one to find any other variances.

Another reason to build security from within the application if at all possible to ensure better results.