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.
Hello, I am having an issue I am trying to solve with a text box in HTML composer. Leading spaces are being added to the number in a string when displayed in a text box on an HTML composer page, but not in the raw XML output, even though || is used for concatenating a $ sign. The number of leading spaces is the length of the number minus the the length specified in the second argument of FTOA. So if the length of that argument matches the length of the number there are no spaces between the number and the $ sign.
DEFINE FILE CAR
FTOA(PLAN_INFO.SEG01.PLAN_ASSETS, 'A20V', 'A20V'), 20, ' ', 1, 'A20V');
COST1/A150V= '$'||FTOA(CAR.BODY.DEALER_COST, '(D12)', 'A50V');
END
TABLE FILE CAR
SUM COST1
ON TABLE PCHOLD FORMAT XML
END
Just a note on concatenation. The strong concatenation || affects the left argument in the expression, removing trailing spaces for that argument, so does not affect leading spaces on the right hand argument which remain in place.
Also the XML produced shows a single space, but a view source will show that multiple spaces in raw HTML are reduced to 1 space when displayed. Try a view source on the XML output and you will see the full multiple spaces that end up in the text box.
Tony's second example is probably the easiest solution.
Alan. WF 7.705/8.007
Posts: 1451 | Location: Portugal | Registered: February 07, 2007
In my opinion, FPRINT is a great function, except for the right-justification. I don't see why it doesn't left justify, there's no logical reason to preserve the leading blanks.
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
Thanks for the quick responses. The suggested formatting worked. I am still fairly new to wf and don't have all the formatting tricks and functions memorized yet, this was very helpful.
WF: WebFocus 8.0.02 InfoAssist, Dev Studio, Magnify, Portal/Dashboards, Mobile Favs Data: DB2 OS: Windows Output: Multiple
Posts: 23 | Location: KC, MO | Registered: August 05, 2013