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 email@example.com for further assistance. Reference the community FAQ to learn more about the community.
The page was generated using HTML layout which contains all sorts of additional attributes and code that is used by IB. It's an absolute hairball from a code viewpoint. I have no idea what the format should be looking like. Normally, I would add normal
code but somehow I have to bind the &WFFMT variable to a control and get it passed via IB's mechanism.
I was able to reimport the fex into the page whereupon it recognized the new amper variable and it created a new control and added it's own coding to the page. Because there are so many "behind the scenes" connections to underlying IB code I suspect that this is the only way I'll be able to add this amper variable and get it to be passed properly. I need to do this with about 75 reports and this is gonna take forever to do with this process. What a complete downer.
I imagine that all the extra attributes in the HTML are related to the WYSIWYG nature of the tool and the special IB back-end connection code. UGH!!!
The code that you suggested would be part of the solution if I was rolling my own page but I need to integrate a new amper variable into a page that was generated with the HTML layout tool and this has all kinds of hooks in it. I needed to use the tool I'm afraid.
I did look at the new code to see the differences and it's just a hairball. Many references and non-standard tags (to me at least)sprinkled around that reference my "wffmt" output element. There are lots of controls, identifiers, and attributes on the page and I'm concerned that I may end up breaking something so I'm gonna just bite the bullet and use the tool to add the new variable/control to the HTML pages.
Maybe you could split the difference (going forward, of course). I've always been a tad confused by those who say they code their own HTML instead of using the tool. As you say, the output is just so dang hairy that I felt it was impossible to do so.
But. I have noticed there seems to be a pattern where all the XML stuff it needs to function is down towards the bottom. Maybe there is a way that you can create a default layout (in your own tools), and apply this layout (thinking the 'Drag your file into this window' default message on a new HTML page create in the HTML Layout Painter). After, use the Form controls to associate to your destination FEX, and then edit the form controls to remove styling and positioning. Seems like it'd work.
Lastly, I know you'd lose functionality, but what about coding a standard HTML form, name your form controls the same as the internal vars, and put your fex destination as the form action? THere'd be more to this, of course, but you see what I mean, right? would this be doable?