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.
190,000 options in a listbox will probably break any web browser. You should consider chaining the listbox with a higher-level control - grouping the contract numbers by region or city for example...
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
That best way to make something go faster is to not do it at all!
From a usability perspective, how would your users interact with 190,000 values in a drop-down list?
Even if you can fine-tune the database retrieval process to make it "fast", the bottleneck will likely your internet browser which may start choking at having to handle all those many values in memory in addition to the actual HTML document you're dealing with.
I would seriously revisit the design to implement something not necessarily easier to develop but absolutely more scalable and with a better user experience.
Perhaps you can break down you contracts into different buckets (groups, categories, etc.) and use some chained controls to load only the subset of contracts applicable to the category currently selected?
In some cases, you may need to go beyond what HTML Composer will let you do out-of-the-box and resort to third-party "widgets" that support lazy-loading via Ajax, for instance.