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 need to wite a generic fex that will be included at the start of any report and grab the passed parameters. The report could be called by caster or by a post (not get) from a launchpage.
I know I can issue -SET &ECHO=ALL; -? &
to see the params... but I want to actually do something with the list, not just display it. Is there a way to cycle through the list of params in DM? Of course the params differ from report to report and the generic fex I need could not contain a list of expected params or anything like that. It must handle whatever is present.
and that is exactly what I am trying to do also. I can do what the original poster did and create a huge param that contains all of the passed params but that would be a major hassle. I will look into that tomcat approach also.
Is there a way to do this now that did not exist in older versions of webfocus?
Thanks
JodyeThis message has been edited. Last edited by: jodye,
Here's an idea sent to me a while ago by Grzegorz. It builds a parameter list on the client side. You'll have to include code like this on every launch page, but you may find this preferable to the server side approach. -James
The idea is to add to HTML form one multiple select element, named PARAMNAMES and the doSubmit() function invoked on the onsubmit event. doSubmit function checks all the form elements, filter them and if the element is "recognized" as a parameter, its name is added to the PARAMNAMES list, so it will be passed as the CGI request (regardless if the method is POST or GET). The FEX can handle the list of the parameter names, and then dynamically construct its own code (which makes the "real" work) using .EVAL.
Hope this helps GrzegorzThis message has been edited. Last edited by: jbmuir,
WF 7.1.6 moving to WF 7.7, Solaris 10, HTML,PDF,XL
Posts: 83 | Location: Dartmouth Hitchcock Medical Center | Registered: April 17, 2003