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.
Hi Francis, It would be very awesome to have such passable parameter to set. So your question gave me some ideas where I could also use portal name. Solution I came up would be catch it on dashboard/launch page with Javascript like this:
function catchTitle(){
var name = parent.document.title; alert(name);}
and then use javascript to populate some hidden field on HTML page. After that you can assign that hidden field value to what ever parameter and send to fex.
In WebFOCUS 5.* and 7.* I have asked, pleaded and opened cases to have the BID View Id as a parameter. On Feb 6, Tech Support wrote: "The issue should of been addressed under WebFOCUS 77 as well but perhaps something got broken between the releases. If you like I can certainly submit your case to programming as a bug again." Then later this: "I believe you specifically want to expose the Portal name to be used in WF 8x. This can be done, but there are certain restrictions. It only works in the Portal itself, and it may not be supported post 8009. The reason is that the back end portal code may evolve and the function might no longer work."
<script type="text/javascript">
alert("The portal name is: " + parent.BipView.gView.getName());
</script>
This is what a BIP page source looks like. Why on earth aren't the variables that are passed to the JSP made available as parameters? &ViewID, &ViewName, &ViewTitle, &SessionTimeout This ought to be really simple for real software developers to do.
MattC, thanks for that link - it looks very interesting. Found any documentation on this?
Tom, I've never seen these tables before. My guess is these masters are custom built to read the WF 7 and older MRE user.htm file. THis has changed completely in WF 8. In any case, this information will not tell me which BIP I'm currently in.
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
The REST architectural style was developed in parallel with HTTP Version 1.1, based on the existing design of HTTP Version 1.0. The largest implementation of a system conforming to the REST architectural style is the World Wide Web. REST exemplifies how the architecture of the web emerged by characterizing and constraining the macro-interactions of the four components of the web, namely origin servers, gateways, proxies and clients, without imposing limitations on the individual participants. As such, REST essentially governs the proper behavior of participants.
This cannot have been written by someone at Information builders. Neither does it make any sense, or is it too early in the morning?
"essentially governs the proper behavior of participants" I thought this is the task of the Thought Police...
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
I dont know if you have solved it or not, but my workaround is following:
I created HTML what catches portal name ( could be what ever variable can be caught with javascript/jquery) and store them in the hidden input fields. After everything is store in the hidden fields I execute procedure where I convert all the parametervalues to global parameter values and then they are ready to use where ever.
Trick here is that I call this HTML on portal banner area, while its hidden or 1x1 size.
For html use the onInitialUpdate function to set parameters:
function onInitialUpdate(){
var Display = parent.BipView.gView.getName();
document.getElementById('inputhidden1').value = Display;
}
Release: WebFOCUS 8104, AppStudio: 8105 OS: Windows Output: HTML,Excel,Active Reports
One of my colleagues came up with this JS, which can be used in BIP pages directly and also in HTML pages launched from a hyperlink located somewhere in the BIP.
// Capture BIP Name and Title
var w = (window.opener) ? window.opener.top : window.top;
if(w.hasOwnProperty('NewPageViewName'))
{
pBipName = w.NewPageViewName;
pBipTitle = w.NewPageViewTitle;
}
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server