As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
This is hardly worth posting, but its a big deal to me and no one else in my shop can appreciate this as much as you folks would.
I just learned that my shop will stop using IE as the default browser (anything that I created needed to work with IE). We're going to be a Chrome shop in the next few months. And its about time right?!?!?
I'm looking forward to using those D3 visualizations. They often had issues with IE.
Yay!This message has been edited. Last edited by: FP Mod Chuck,
HEX YAYUH!! CELEBRATE GOOD TIMES!!! haha Nice man! We are finally on board w/Chrome at our site too now. Took some convincing and for things to begin breaking, but we're there pretty much. haha
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
Originally posted by Doug: That beckons the question: Why isn't IE Being kept up to Chrome. I have one section of one portal that messes up IN IE, and looks fine in Chrome.
Well that's one I can answer. 'Cause MS has Edge now. I'm guessing that IE isn't even supported by MS anymore. I haven't tried, but I've heard that Edge has a whole host of problems with webfocus too.
- IE is no longer supported by Microsoft with feature updates. Hasn't been for some time. - MSFT's Edge browser is transitionary in that it is still based on their EdgeHTML engine. - Either a newer version of Edge or a brand new browser will be replacing Edge soon that is based on Chrome's Chromium engine. EdgeHTML is dead.
One should also know that HTML5 (and CSS3) is considered a living standard and there will be no more versions (No HTML6 nor CSS4). That’s why the DOCTYPE for HTML5 doesn’t have a “5” in it:
So now in HTML and CSS, the technology is not versioned and instead we just have a living document that defines the technology as it evolves.
Browser engines must keep up with the new technologies and implement them. Where Microsoft has not updated the IE engine for nearly four years, it will not be able to render pages that are using the current HTML Living Standard
...and once you do move to Chromium.Blink, because it's a when & not if, you can keep up to date via the Chrome Platform Status site for a release schedule and features list as well:
We are finally going that way as well. We are in the testing phase. I have one question. Almost everything we use is Excel. We don't open excel in the browser, we open in Excel. When I run from Chrome, I get a "Save As" diaglogue and it want to save in the Downloads folder. Can I get these to open in Excel like IE?
In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006
Here is some information from our site regarding Chrome compatibility:
A change in the way Chrome works has caused it to stop respecting the XMH format as a Web Archive. A combination of two settings is required to resolve this problem:
Use SET WEBARCHIVE = OFF to change WebFOCUS processing from XMH to XHT format.
Change the Redirection Settings for the XHT format to Yes/Yes to redirect and
save the report to XLS format.
1. SET WEBARCHIVE = OFF
You can specify the command either directly within the .fex procedure itself
or you can specify the command within the edasprof.prf. Placing the command
within the edasprof.prf file allows it to be globally enabled for all
requests.
To set the command in the edasprof:
http://server:8121 (for a default installation)
Click Workspace and then Expand Configuration Files
Right click "Server Profile - edasprof.prf
Add SET WEBARCHIVE = OFF to a new line at the bottom of the file.
2. To set the Redirection Settings:
http://server:8080/ibi_apps/
Click WebFOCUS Administration Console
Expand Configuration
Click Redirection Settings
Change the settings for .xht format to Yes and Yes
Click Save at the bottom of the page
Click Clear Cache at the top of the page.
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
BabakNYC, thanks for the info, but those are EXL2K formats not XLSX formats. While we have a few EXL2K left, almost everything has been converted to XLSX, but I'll give this a try for the EXL2K Reports.
Here's what I found: 1. Download the file once; 2. When finished, at the bottom of the screen is a status, click the little arrow, the select "always open files of this type". So far this works like a champ. The file is still downloaded but it automatically opens. 3. Do this for each file type you use.
In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006