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 have a lot of parameterized html pages that contain listboxes of codes (Service, Discount, Package Etc..) The codes can be setup using any combination of enterable keyboard characters like the dollar ($) sign. I have realized that having a dollar sign in the WHERE clause causes the dollar sign in the generated SQL to be masked.
For example code 3$: The SQL statment would be WHERE SERV_CDE LIKE '3_ ' instead of WHERE SERV_CDE = '3$' I now understand why this occurs and the other masking behaviours using $ and * together. We use the IF logic with EXACTLY to get around it but, it would be simpler if we could turn off the masking behaviour with some type of configuration setting similar to HTMLENCODE.
I was wandering if there is a setting to turn off the masking behavour associated with the $ sign?