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'm a bit frustrated because I have gotten this to work a couple times, but I simply cannot recreate it.
I am using the HTML GUI builder to build a simple front end that contains 5 drop-downs. They are all backended by FEXs. The basic idea is that the user selects an option from the first and only sees options in the second pertinent to the first (and so on down the line). When you get to the last option, you can only see the values that exist where all the previous values equal what's selected. I can get this to work fairly easily, there is no magic.
Due to a customer requirement, I created another level that, in effect, has a drop-down that fills based on another criteria.
Recap: BTW, This is supposed to represent the field label and drop-down box: Label Name: [______________][V]
After the customer was demo'd the question came up, "Well what about Service Lines? (a missed requirement). Service Lines are peers of units. Groups of them, if you will. So now the front end looks like so:
[Select By...] is a static drop-down that has three entries, ERROR (Select By...), Unit and Service Line. Unit and Service Line pass (as values) the field names as they sit in the database.
Here's whats supposed to happen. When a user selects an Entity and 'UNIT', they will see only Units for that entity. If they select Entity and 'Service Line', only Service Lines for that Entity appear.
What I am finding is that the drop-down chaining seems to only support one control chained to another, where this case calls for 2 parent controls be chained to the same child (whereas the other situations are sort of like stair step, 1 -> 2 -> 3 -> 4 (etc) situations).
I've gotten it to work a few times (as intended), but I've made some changes to my Report Fex that is called as the hyperlink destination and I have to reimport it for the new parameter field to be seen and when I do, the wheels fall off. It seems like I have to attempt this 5-10 times and eventually it works. I know a poor developer blames his tools, but I'll run that risk. Any ideas?
No, not the only one; here's an example I put together a while back and updated a bit just now. I've removed some of the extra fluff from the form code so as make it easier to read, and trouble-areas of the code are highlighted.
Here's the form that's built:
ChainExample_CountryList.fex
TABLE FILE CAR
PRINT COUNTRY
BY COUNTRY
ON TABLE SET HOLDLIST PRINTONLY
ON TABLE PCHOLD FORMAT XML
END
ChainExample_BodytypeList.fex
TABLE FILE CAR
SUM BODYTYPE
BY BODYTYPE
ON TABLE SET HOLDLIST PRINTONLY
ON TABLE PCHOLD FORMAT XML
END
ChainExample_CarList.fex
TABLE FILE CAR
PRINT CAR
BY CAR
WHERE COUNTRY EQ '&country'
WHERE BODYTYPE EQ '&bodytype'
ON TABLE SET HOLDLIST PRINTONLY
ON TABLE PCHOLD FORMAT XML
END
ChainExample_CarInfo.fex
TABLE FILE CAR
PRINT COUNTRY CAR MODEL BODYTYPE
SEATS DEALER_COST RETAIL_COST
WHERE COUNTRY EQ '&country'
WHERE BODYTYPE EQ '&bodytype'
WHERE CAR EQ '&car'
ON TABLE PCHOLD FORMAT HTML
END
<input id=IBIMR_domain type=hidden value=robwagne/robwagne.htm name=IBIMR_domain>
<input id=IBIMR_dir type=hidden value=#bannerreport name=IBIMR_dir>
<input id=IBIMR_folder type=hidden value=#testreportst name=IBIMR_folder>
<input id=ibif_ex type=hidden value=app/chainexample_launchpage.htm name=ibif_ex>
<input id=ibiapp_app type=hidden value=gold name=ibiapp_app ismre="1">
<input id=ibic_server type=hidden value=WFNT name=ibic_server>
</form>
<iframe id=report1 title=app/chainexample_carinfo.fex tabIndex=-1 name=report1 elementtype="2" autoExecute="False" WIDTHOLD="610" HEIGHTOLD="280" requests_list="0" executebuttonId="form2Submit">
</iframe>
<!-- ***** User instructions: ***** -->
<div id="divReportInfo">
<h1>Data:</h1>
<p>
This report demonstrates list box chaining where one list box is
fead by multiple inputs.</p>
<h1>Parameters:</h1>
<h2>Country</h2> - This independent parameter feeds both the Car list box and the final report.
<p />
<h2>Body Type</h2> - This independent parameter feeds both the Car list box and the final report.
<p />
<h2>Car</h2> - This list box is populated based on your selections for Country and Body Type.
<p />
</div>
<!-- End instructions -->
The values for attributes should typically be as shown, except "inchainindex" which should increment starting with 1 for each list box in the chain.
Each of the listboxes in the chain must be listed in the hidden "layoutinfo" input, as well as in the window.chain0 variable.This message has been edited. Last edited by: MathematicalRob,
WebFocus 8201m on Windows; App Studio 8201; Procedures: WebFocus with SQL; HTML Parameter Pages & Dashboard; Output: Excel, HTML, & PDF.
Posts: 88 | Location: MI | Registered: July 23, 2009