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.
I am using WebFocus Maintain Forms for users to enter data and look-up information. I do not use dashboard. Some users, out of habit, click the browser "Back Arrow" button when they want to go back to the previous form. This disconnects them from the server and forces them to reconnect by starting a new WebFocus session. Has anyone come up with a way to get around the disconnect when a user clicks the "Back Arrow" button? Thanks, KentThis message has been edited. Last edited by: Kerry,
Windows2003 Server, WebFOCUS 7.7.02 Developers Studio and MRE
Posts: 63 | Location: Ft. Wayne, IN | Registered: February 20, 2007
Kent The reason for the disconnect is because the application has a persistant connection to the server. If the user clicks on the arrows the application will disconnect. We have found that the only way to truly stop the user from clicking on the arrows is not to display them.
You can launch Maintain in window without the toolbars. Here is an example of the code to do that. Create an HTML Launch page or add this code to your existing page.
Mark
<html>
<body onload="launchMaintainProc();">
<script language="JavaScript">
function launchMaintainProc()
{
var getRandomNum = Math.random();
var launchURL = "/ibi_apps/WFServlet?IBIS_connect=on&IBIAPP_APP=ibisamp";
launchURL = launchURL + "&IBIC_server=EDASERVE&IBIC_user=anyone&IBIC_pass=anyone";
launchURL = launchURL + "&IBIF_cmd=MNTCON+APPPATH+IBISAMP;MNTCON+EX+MNTIVP;";
launchURL = launchURL + "×tamp=" + getRandomNum;
window.open(launchURL,"_blank","toolbar=no, menubar=yes");
var ie7 = (document.all && !window.opera && window.XMLHttpRequest) ? true : false;
if (ie7)
{
//This method is required to close a window without any prompt for IE7
window.open('','_self','');
window.close();
}
else
{
//This method is required to close a window without any prompt for IE6
this.focus();
self.opener = this;
self.close();
}
</script>
</body>
</html>
Posts: 663 | Location: New York | Registered: May 08, 2003
And still, the user might still be able to hit the backspace button. And when the cursor is not on any element of the document, but for instance on the form itself, it is actually the same as hitting the back button. The app will disconnect when that happens, just as when the back arrow is clicked. I have created a small javascript to prevent that. Here it is:
document.onkeydown = catchIt;
function catchIt() {
var curelem = document.activeElement.name;
if (window.event.keyCode == 8) {
if (typeof curelem == "undefined") { return false; }
return true;}
}
Bind it to the form and backspace button usage will be restricted to active elements only. No more unwanted disconnects.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007