• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums User Experience Lawson Portal

Internet Explorer 7 testing

 5 Replies
 0 Subscribed to this topic
 14 Subscribed to this forum
Sort:
Author
Messages
beverly godwin
New Member Send Private Message
Posts: 0
New Member
2/17/2009 10:09 PM

How extensive should we be testing the IE 7 with lawson? i.e. should we perform every function in GL/AP/PR/HR/PA/BN, etc., or do we merely need to go to a few pages and try out some actions?

What types of problems have people found with IE 7?

We are on envir 8.0.3.7 and apps 8.1.  We also have Ess/Mss.

Thanks for any assistance.

k-rock
Veteran Member Send Private Message
Posts: 142
Veteran Member
2/18/2009 4:06 AM
in my experience it was easier to always do a full set of testing. I developed a set of tests that could be completed by 1 person in 2-3 days that tested every function of GL. No matter what we were doing, we ran the full set, the kept us from overlooking something.
Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
2/18/2009 4:44 PM
please be aware that any application piece using DSSO (LBI, MSCM, others) will probably not work correctly without some modifications to the time out value for IE7.
Documentation for adjusting this timeout value can be found in KB #5272995 on Lawson's support site.
Christi
New Member Send Private Message
Posts: 2
New Member
3/2/2009 3:32 PM
Our upgrade (apps and env) from 8.03 to 9.0 included a change from LID to Portal. The upgrade testing was completed on IE 7.0.
Only issue that we came across (so far) was for employees with Google Task bar- it had to be uninstalled in order for the status bar to work properly.
Maris Fisler
Basic Member Send Private Message
Posts: 8
Basic Member
3/2/2009 3:35 PM
I have been using IE7 since before Lawson certified it and have only had problems with the Status bar not working (not showing the Change-Complete or Add-Complete and only saying Done) until you go into your Internet Option/Security and set the Allow Status Bar Updates via Scripts to be Enabled. In fact once we went to LSF9 updating to IE7 was the only way to fix some other issues that the Users were having.
Deleted User
New Member Send Private Message
Posts: 0
New Member
3/3/2009 2:07 PM

How much to test, for a "supported" brower is, well, up to you. If its supported officially by Lawson, everything should work, right?? ...................

If you are pressed for time, this what I would do.

1. Do a search on Lawson's web site for all KBs related to IE7, for your platform and version. Then, test those, and note the changes you need to make. For example, the status bar issue.

2. Test your critical processes. Ex. Make sure you can enter a JE, reverse, and close GL. In AP, make sure you can add an invoice all the way to print out checks.

3. NOTE very clearly, only the essential tasks were tested, in case (and it will happen) some manager asks later, why didn't you do it? Well, there was no time.... 

If you are not pressed for time, still do step 1. then, test everything you use at your company.

Regardless of which approach you take, do NOT speed up testing by cutting corners, you will end up scrambling on go-live date.

hope this helps! 

MTFF