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 a portal issue that is making me crazy, any help would be greatly appreciated......
I have a Portal, it contains about 8 tabs with multiple reports on each tab. My Banner is to the left and contains a html form that contains all parameters for the reports, one of the parameters is a location drop-down list that is populated with a fex. The values in this drop-down list are determined by the security levels of each user logging in to the portal. My reports all run fine and the html works fine and passes the parameters with no issues. The problem is on the first run (Load) of the portal and all the reports. What I need it to do is run the html first and use the top value of the location drop-down to populate the reports with. Currently I have a default value in the fexes and this is what the reports display on load, this is an issue because of the security. Not everyone can see the same locations. I don't have a single location that everyone is allowed to see that I can use as a default, so I really need to figure out a way to make the reports read the first value of the drop-down list when the portal loads, has anyone else run into this? I have opened a case but no answer yet.This message has been edited. Last edited by: <Emily McAllister>,
have every fex that runs on load to call the fex the loads the location dropdown and limit it to show the first record. Then do a readfile where you can load the parameter with the location in it. Pass that parameter to the calling fex.
WebFocus 8.1.5 iSeries/Windows DB2/SQL/Access Dev Studio App Studio Maintain ReportCaster
Posts: 341 | Location: Pembroke NH/Jericho NY | Registered: June 15, 2011
You can also have a fex included in the _universal_profile that will assign a global variable (&&var) having the security location defined for the login user (and as many other variable that you want) and then use that variable to populate your reports.
Per example you will have at the first step of each report:
-* If &&SECURITY_LOC from _universal_profile fex gives access to ALL location based on user security,
-* verify if user have selected a location on HTML otherwise show ALL location.
-* If &&SECURITY_LOC from _universal_profile fex assign a specific location based on user security, then show only that location
-SET &HTML_LOC = IF &&SECURITY_LOC EQ 'ALL' THEN (IF &HTML_LOC EQ 'ALL' THEN FOC_NONE ELSE &HTML_LOC) ELSE &HTML_LOC;
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
Originally posted by Jay Potter: have every fex that runs on load to call the fex the loads the location dropdown and limit it to show the first record. Then do a readfile where you can load the parameter with the location in it. Pass that parameter to the calling fex.
Jay, Thank you I didn't think of that. I will give it a try.
Originally posted by MartinY: You can also have a fex included in the _universal_profile that will assign a global variable (&&var) having the security location defined for the login user (and as many other variable that you want) and then use that variable to populate your reports.
Per example you will have at the first step of each report:
-* If &&SECURITY_LOC from _universal_profile fex gives access to ALL location based on user security,
-* verify if user have selected a location on HTML otherwise show ALL location.
-* If &&SECURITY_LOC from _universal_profile fex assign a specific location based on user security, then show only that location
-SET &HTML_LOC = IF &&SECURITY_LOC EQ 'ALL' THEN (IF &HTML_LOC EQ 'ALL' THEN FOC_NONE ELSE &HTML_LOC) ELSE &HTML_LOC;