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 have a question ( and if not available an enhancement request ).
When a fex is executed you get an HTML page "Waiting for response...". But that is all it tells you... I found this page on my local machine and enhanced it with some script to -at least- show when the fex was started.
Is it possible to make a page like this:
Waiting for response... Fex : alg_0000_demo.fex User : davevissers Started : 09-08-2010 11:50
Technically that should not be too hard.... Studio ( or dashboard ) could call the html page using: PendingRequestPage.html?&fex=alg_000_demo.fex&user=davevissers&dt=09-08-2010%2011:50 right?
With some scripting that can be made visible, even with plain HTML.
Does anyone got something like this working?
This would be especially helpful for our dashboard users.
Greets, DaveThis message has been edited. Last edited by: Kerry,
_____________________ WF: 8.0.0.9 > going 8.2.0.5
Posts: 668 | Location: Veghel, The Netherlands | Registered: February 16, 2010
The "please wait" topic has been discussed many, many times with multiple techniques described.
However, what seems like a simple page to create, as you describe, is not really within the processing flow of how WF works.
When the user submits a request, the client sends it off to the WF server, where numerous things could occur. It could be executed immediately. It could be delayed or queued if all agents are in use or priority is low. It could possibly require new agents to be started, etc., etc. However, there is NO communication back and forth between the server and the client until an answer set (or an error message) is returned. So there would really be no way to display a time/date for when a procedure actually was started. I suppose the client could be enhanced to display a time/date a procedure was submitted, but that really tells you nothing that you don't already now. Might as well say "Started: Now" So technically, it is a little more complicated than it seems. Hope the explanation makes sense.
Regards,
Darin
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
But when I have 3 different browsers all saying "Waiting... "
With no indication which is which... just a starttime ( what I've already managed by scripting ) and a fex-name would be helpful.
Especially for the end-users. They might want to start 4 queries. But there is no way to see what is already running... resulting in: Just to be sure, let's start it again.
That's what I'm trying to prevent with a fex-name. ( including the used parameters would be even better )
Hope you understand.
_____________________ WF: 8.0.0.9 > going 8.2.0.5
Posts: 668 | Location: Veghel, The Netherlands | Registered: February 16, 2010
That makes good sense as well. So you're not as concerned about WHEN the job actually gets submitted to the server as much as identifying the job that has been submitted in a specific browser window. That seems to be something that the WF client could handle on submission. (Including parameters would still require parsing somewhere - maybe more of an issue.) I would open a case for a new feature request.
Regards,
Darin
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007