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 an HTML front-end that calls a fex to display a simple PDF report. The PDF report is drill-through enabled by calling another fex. The WebFocus components work fine together, but when the HTML is in front, everything breaks down. The process runs perfect when called from MRE.
I have ironed out most of the issues, but I am still having problems with 2 drop-down variables. In the first fex, if I put a -TYPE on these variables and EXIT at the beginning, they display fine with the correct values. If I don't do that, they display the appropriate values in the Fex at the appropriate times. When it gets to the querystring portion, it doesn't display the variable values. No error, just no variable displayed. The variable I am using in the query string display is the same as I am -TYPE ing above.
Does anything jump out at you?
-ABTThis message has been edited. Last edited by: ABT,
I'm confused. Are you talking about controls not being populated on an HTML launch page? If yes, is the master you are looking at to populate the boxes in the application path?
No, the HTML page works fine all controls are displayed, populated and send appropriate values to the destination FEX file.
Once in the destination FEX file, I can -TYPE the variables passed to see they made it and what their values are. All is fine in this step also. At the bottom of this FEX, I structure my output as a drill-through. In setting up the destination and it's QueryString parameters, several of the variables are acting as if they are empty.
&PROVSTAT and &PROVROLE are represented as drop-down items on the HTML page. Again, when I -TYPE the vars above, they show the correct data. When looking at the output of the PDF (hovering over the links), I can see the values are not listed.
-ABTThis message has been edited. Last edited by: ABT,
I just realized that! Yes, unfortunately, you cannot embed other tags within the code tags.
The styling line may be too long, try breaking it into multiple lines using the \ continuation character. Also, all alpha strings passed as values in the drill-down link must be within quotes: