Our company plans to upgrade to IE11 soon.
Has anyone experienced issues with IE11 and CA PPM 14.2
Attached are the 2 items that we have identified.
Not seeing either of these problems.
On IE11, CA PPM 14.2.
Have not identified any other problems, except that it seems that Browser History Setting for "newer versions of stored pages" must be more strictly enforced, setting it to "Every time I visit..." This is generally our default setting, but after upgrade, we have had numerous calls where user could not bring up their login page and found that their browser had the wrong setting - typically finding it set to "Automatically."
Most of our users are still on IE10, with plans to upgrade them to IE11 by year's end. On previous versions, have found similar types of problems as you mentioned here, though not exactly the same two that you have had.
Yes we have had an issue with IE11. We noticed within a Cost Plan, you cannot edit future dates. Lets' say the project is from 10/15 to 12/18. If the user tried to enter values in say 11/18, the page would "bounce" and not allow the user to edit the field. I believe there is a patch for this. As a work around and this might sound strange, I found that if you zoom out to say 75%, the user is able to edit the field.
There should be an official patch for this. Sorry I just don't know the name/number of it.
We import our cost plans from external source - so, had not tested manual editing.
Tried it now. Can edit properties, but can't edit details. "Allow Editing" is enabled for the virtual/time-scaled values. I have cost plan edit rights. Tried zooming in/out, changing compatibility settings, changing browser emulation modes - no difference - can't edit the time-scaled values of cost plan.
I don't know that this is a browser issue, but it is an issue.
We had plenty of issues with IE11 before upgrading to 14.2, but so far haven't had any in our testing. We are about to do for production upgrade this weekend so I'll report back if we get any surprises next week, but so far the biggest issue has been some testers having to do a full cache clear before the page would come up initially, but once they were in they were fine.
we had the same issue that people could not log in after we upgraded to 14.2, but we had them clear their cache/start a new session and ensure the 'Preserve Favorites' box was not checked and everyone could log in. I am aware of the setting to refresh the page each time you visit, but did not realize it could have contributed to this too.
We are not having issues with cost plans, but the inability to edit/scroll was found in 13.3. CA said we had to change the time scale to be "start at cost plan start date" but that was not an option. We did have to use the Time Scale option to be set to Other time scale: Period Type, but we kept start date of Rolling date - current month. Then, we took off the Time period offset- *the key was to not have a scroll bar and we had a 12 months view).. and the problem went away. In 14.2, CA did make fixes to this defect, but the resolution is not clear. It is listed on the fixed defect list .
For the missing login page, we focused our solution on what we knew from the past - we've had instances in the past where "Automatically" failed users on other CA PPM screens. Not a big, frequent problem, but persistent over many years. Changing to "Every visit...." solve the problem, at least until a user got a new machine with a fresh IE install.
I tried some of your Cost Plan changes - none worked. But frustration bore fruit - I finally tried "Restore defaults" .... Wunderbar! It works! (actually, I said "Doh!!!" having a Homer moment.)
Your suggestions didn't work, but they got me on the right road to a solution.
Need to clarify -- they are actually not my suggestions. CA has a TEC article on this issue, but I did not agree with their workaround, since we have some cost plans that are 5+ years, I can't ask our users to scroll through 5 years to get to the current month!
So ours was messing with what we see as a defect and doing what we could to make it work.
But, again, they do list one of the articles as "Fixed" in 14.2, which is odd , since we were told it was not a defect, but I have no idea what they fixed!
Retrieving data ...