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.
When trying to use &IBIC_user , I can get it to evaluate correctly when running in Dev Stu, but when I use the exact same code within Dashboard it gives me (FOC295) A VALUE IS MISSING FOR: IBIC_user
-SET &IB_USER = &IBIC_user ; -TYPE &IB_USER
Is there a setting for MR/Dashboard that I need to know about?
Posts: 55 | Location: UK-London | Registered: January 27, 2005
IBIC_user is the HTTP request parameter. If you would like to use it within a focexec, you could do the following settings:
put the following lines into the site.wfs configuration file (located in IBI_HOME/client53/wfc/etc): <set>IBIC_user(PASS)
restart the web server (or reload the ibi_apps web application)
After that, you will have the &IBIC_user amper variable in fex procedures, containing the value of the IBIC_user request parameter. (I suppose, that in your current configuration you have the <set>... settings (or equivalent) configured within DevStudio, but not in the web client configuration)
If It's 5.3x definitely make your changes in the Administrator and not manually. It seems to cause problems when you do it the old fashioned way in 5.3.