If you are on OBIEE 11.1.1.1.7.0 / 11.1.1.7.1, you might be interested in patch 17606196. It should be installed on top of OBIEE 11.1.1.7.1 and covers Chrome 30 & IE 10 problems:
16068402:GRAPHS NOT SHOWN ON IE WHEN OBIEE IS BEHIND A REVERSE PROXY
16667503:QA: PROMPTS: RESET TO LAST APPLIED VALUE IS NOT WORKING
16371801:QA: IE10: GAUGES VIEW OVERLAPPED WITH OTHER VIEWS
16455904:QA: IE10: SLIDER PROMPTS CANT SLIDE TO LOWEST LIMIT
16382296:QA: IE10: MAP VIEW SHOWS SERIES OF ERRORS
16402964:QA:IE10: NEW CONDITION THROWN ERROR"OBJECT DOESN'T SUPPORT PROPERTY OR METHOD'
16391455:QA:NEW AGENT PAGE IS NOT DISPLAYED IN IE10
16390205:QA: IE10: RESIZE COLUMN SELECTS ALL TEXT IN TABLE/PIVOT VIEW
16389347:QA:UNABLE TO OPEN OR CREATE A KPI WATCHLIST USING IE10 BROWSER
16389210:QA: CAN NOT CREATE OR OPEN A SCORECARD WITH IE10 BROWSER
16382198:QA: IE10: ANALYSIS PROMPT FOR HIERARCHY: VALUE TEXTBOX NOT FULL SIZE BUT WORK OK
16371672:QA: IE10: FREEZE HEADER: LONG SCROLL SHOWS TRIMBUFFER ERROR
16371553:QA: IE10: SIGN IN PANEL IS NOT AT CENTER POSITION
15935506:IE10 NOT ABLE TO CREATE OR EDIT AN ANALYSIS IN ANSWERS
16667503:QA: PROMPTS: RESET TO LAST APPLIED VALUE IS NOT WORKING
16371801:QA: IE10: GAUGES VIEW OVERLAPPED WITH OTHER VIEWS
16455904:QA: IE10: SLIDER PROMPTS CANT SLIDE TO LOWEST LIMIT
16382296:QA: IE10: MAP VIEW SHOWS SERIES OF ERRORS
16402964:QA:IE10: NEW CONDITION THROWN ERROR"OBJECT DOESN'T SUPPORT PROPERTY OR METHOD'
16391455:QA:NEW AGENT PAGE IS NOT DISPLAYED IN IE10
16390205:QA: IE10: RESIZE COLUMN SELECTS ALL TEXT IN TABLE/PIVOT VIEW
16389347:QA:UNABLE TO OPEN OR CREATE A KPI WATCHLIST USING IE10 BROWSER
16389210:QA: CAN NOT CREATE OR OPEN A SCORECARD WITH IE10 BROWSER
16382198:QA: IE10: ANALYSIS PROMPT FOR HIERARCHY: VALUE TEXTBOX NOT FULL SIZE BUT WORK OK
16371672:QA: IE10: FREEZE HEADER: LONG SCROLL SHOWS TRIMBUFFER ERROR
16371553:QA: IE10: SIGN IN PANEL IS NOT AT CENTER POSITION
15935506:IE10 NOT ABLE TO CREATE OR EDIT AN ANALYSIS IN ANSWERS
The first bug, 16068402, has a specific patch 16068402, but I didn't see patch 17606196, replacing it formally.
No comments:
Post a Comment