Focal Point Banner


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.



Read-Only Read-Only Topic
Go
Search
Notify
Tools
Drill down Fexes
 Login/Join
 
Member
posted
i have an issue with all my drill down Fexes, where there is no indication that the second fex is running when the users click on the drill down, so they keep clicking multiple times because it looks like nothing is happening
this is causing all the agents to be used up so that no one else can get into WebFocus (no agents available). Any ideas on how to get around this?


7.6.4 reporting server running on iseries 5
http server windows platform
 
Posts: 2 | Location: Hanover, PA | Registered: July 17, 2008Report This Post
Virtuoso
posted Hide Post
A quick "fix" would be to add a TARGET=_BLANK attribute to each of your FOCEXEC style setting so the drill-down opens in a new window, which even if slow will give your users an indication that something is happening.


If you want them to open within the same page though and your underlying calls are a bit slow, you may need to resort to more elaborate means like using wrapper .fex/.htm file to display some notification of stuff happening while the HTML document's href is silently being redirected to the actual WFServlet call executing your report, or perhaps using JavaScript routine instead of direct FOCEXEC calls in your drill-downs. That way, you can use your JavaScript piece to display a "Running..." message somewhere in your page to later change the document's href.

Just keep in mind that adding all of this JavaScript baggage will make your code not only more difficult to maintain (although perhaps providing a better user experience) but it may affect the behaviour of the "Back" button in your browser in case users want to return to the main report page; you'll pretty much have to built a lot of custom JS code to make that happen seamlessly.

TARGET=_BLANK may provide a faster win.

You can always try and train your business users to be extra patient Smiler



Prod/Dev: WF Server 8008/Win 2008 - WF Client 8008/Win 2008 - Dev. Studio: 8008/Windows 7 - DBMS: Oracle 11g Rel 2
Test: Dev. Studio 8008 /Windows 7 (Local) Output:HTML, EXL2K.
 
Posts: 1533 | Registered: August 12, 2005Report This Post
Expert
posted Hide Post
There should be an immediate indication in the status bar. Howver, the "TARGET=_BLANK may provide a faster win" and is a fine idea.
 
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders