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.
We are in the process of trying to upgrade to 8.2 and we have noticed that our HTML files that contain the !IBI.amp.HTMLDATESTART ; type syntax are not able to be ran. Has this functionality been removed or restricted? Has anyone else ran into this issue and been able to work around it?
This was the only way we know how to default controls like calendar controls to certain values, so we would like to keep this functionality if possible.
Also, the error we're receiving is an alert that says "User does not have permission to run Portal Content"This message has been edited. Last edited by: FP Mod Chuck,
WF 8.2.0.3 Windows 10 64bit HTML, AHTML, PDF, Excel
The ability to use a variable in a web page is an important component of many of our -HTMLFORMs and I believe for other IB customers, so I don't think it would go away.
The syntax in the 'Developing Reporting Applications' shows 'AMP' to be in caps, and the semi-colon to immediately follow the variable name.
You guys are right. It appears the syntax was not sensitive in our current version (8105). After changing to all caps and moving the semicolon, the error went away.
Though I did not test which specific change corrected it.
WF 8.2.0.3 Windows 10 64bit HTML, AHTML, PDF, Excel