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.
As a developer, you always want your applications to end cleanly. Disconnects, abnormal terminations, and errors can lead to unsaved data, corrupt databases, and hanging agents. When users enter data onto a screen and hit “Save,” the last thing they want to see is that the session has timed out. The technique I am about to describe takes the worry out of that.
If you have ever used an online banking system, and have been idle too long, a message pops up on your screen asking if you need more time. That is what we are going to do here.
A nice thing about this technique is that you can either create a JS procedure and embed it in your forms or edit the MNTONLOAD.JS procedure and place it in there. Anything placed in that file is automatically included in every executed Maintain procedure. The only thing you have to do is place the button on your form.