IE8 issues fro Comments

RT Users
1

Many folks at our University use IE as part of their jobs because our
ERP vendor (Oracle’s PeopleSoft) requires it.

As folks have upgraded to IE8 we are getting calls that Comments are
being truncated without notification for those adding them via IE8
browser.

Has anyone else seen this issue or have an idea of a setting I can
adjust in either RT or IE8. They have already tried the compatibility
option within IE8 with no success.

We are on Rt version 3.8.2

Thanks in advance

Joe Kirby , Assistant Vice President, Business Systems
Division of Information Technology (DoIT)
Support Response - http://www.umbc.edu/oit
Administration 627
Office - 410-455-3020
Email - kirby@umbc.edu

2

Many folks at our University use IE as part of their jobs because our
ERP vendor (Oracle’s PeopleSoft) requires it.

As folks have upgraded to IE8 we are getting calls that Comments are
being truncated without notification for those adding them via IE8
browser.

Has anyone else seen this issue or have an idea of a setting I can
adjust in either RT or IE8. They have already tried the compatibility
option within IE8 with no success.

We are on Rt version 3.8.2

We’ve made a number of improvements since 3.8.2. Can you please upgrade
to 3.8.7 and see if that fixes it?

signature.asc (197 Bytes)

3

I am hoping to use your recommendation as reason to upgrade before
Summer 2010
Thanks for the prompt response

JoeOn Feb 17, 2010, at 11:39 AM, Jesse Vincent wrote:

On Wed 17.Feb’10 at 11:22:32 -0500, Joe Kirby wrote:

Many folks at our University use IE as part of their jobs because our
ERP vendor (Oracle’s PeopleSoft) requires it.

As folks have upgraded to IE8 we are getting calls that Comments are
being truncated without notification for those adding them via IE8
browser.

Has anyone else seen this issue or have an idea of a setting I can
adjust in either RT or IE8. They have already tried the compatibility
option within IE8 with no success.

We are on Rt version 3.8.2

We’ve made a number of improvements since 3.8.2. Can you please
upgrade
to 3.8.7 and see if that fixes it?