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.
However, the example you gave is bad. The / and . do not need to be encoded in this circumstance as they are being used for their reserved purpose. You have to differentiate between a reserved character doing it's job and one that should be encoded.
Alan, thanks. I was just following the example of the WF HTML editor, which URL-encodes the domain folder in the hidden input tags. I guess I shouldn't be too surprised since WF html code is anything but standards-compliant.
SomeUsr, the idea was that WF would do the encoding b/c I'm trying to parameterize the domain being used: one for development, one for production. That way I'd have the same code on both platforms. I know how javascript works...that would have been another option, though less desirable.