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.
In 8201M, we're trying to launch a portal from a link (in a report) that contains a member number parameter. We were able to do this in 8.1 using a link like this in a report... https://servername:8443...&MEMBER_NUMBER=88816
This would launch the member profile portal and load the information (filter all the widgets) for the member whose number was 88816.
The link above does not work for us in 8201M and we're looking for a solution - we got the portal to launch in 8201M but it does not recognize the MEMBER_NUMBER parameter.
We are trying to avoid the method of calling a fex first and writing out the parameter(s) to a file and then having the widgets read the file to get the parameter(s).
Thanks.This message has been edited. Last edited by: mcarey,
WebFOCUS 8202, 8203, Windows 2012 R2 SQL Server 2016, App Studio 8202, 8203
Posts: 17 | Location: Jericho, NY | Registered: February 18, 2014
Unfortunately, this approach didn't work for us in 8201M. Also, we had a case open and were told that passing parameters into a portal cannot be done at this time in 8201M.
WebFOCUS 8202, 8203, Windows 2012 R2 SQL Server 2016, App Studio 8202, 8203
Posts: 17 | Location: Jericho, NY | Registered: February 18, 2014