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 wish you could tell what environment/domain that the file you're working in is from.
I have heard of developers working on a file that they thought was from a Development Environment only to find out they were actually in Production. Ouch.
It would be nice if you could set the background color based on the environment of have the eda/app path of the file in the Header of the edit screen like the explorer does.
There you go, anyone agree?This message has been edited. Last edited by: Kerry,
Don, unable to see Francis/GamP suggestion? Put a global in your profile identifying it as development, and add a -type referencing that && at the start of your fex. But you should be able to detect it from Dev Studio. Ira