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.
I have an HTML Document/Parameter page, created with App Studio. This is inserted into a panel on a portal page.
There is an existing hidden input tied to an existing parameter/variable. I'm trying to change the variable name.
When I do, it unbinds the variable and disables the Tasks & Animations events. The result is, the objects in the tasks no longer refresh the portal page.
I've been working on this for hours and can not find away to re-enable the T&A functionality.
Has anyone else experienced something like this and were you able to recover?
Thank you,This message has been edited. Last edited by: Don Garland,
I found that the best way to change variable names used in a parm page is to change them in the fex, using -DEFAULT, removing the associated task, and re-input the fex. This, I found, changes whatever was using the old variable.
In FOCUS Since 1983 ~ from FOCUS to WebFOCUS. Current: WebFOCUS Administrator at FIS Worldpay | 8204, 8206
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005
I haven't used the requests section to pull in the fex because I worried about corrupting the HTML Doc. This page is particularly painful to loose and rebuild. It's a prototype and features were added daily, so a lot of movement.
But, you are right, I try it. I hadn't thought of this as a way to recover from a crashed.
In my main fex, I changed the -DEFAULTH to -DEFAUT to enable prompting. I added the external procedure under the "Requests -> parameters" option.
The HTML page converted my existing manually created parameters (dashed lines) to externally created parameters (solid lines).
Looks like it's working as described in the manuals.
I think this post taught me that although I'm trying to create things in the GUI, I'm still holding on to old-school methods. It's time to drink the rest of the Kool-Aid
on one hand, WebFOCUS must compete with Tableau and Click View etc etc etc etc etc. which means there must be a fair amount of robust, fancy point and click, drag and drop stuff.
On the other hand, the capability to write code behind the scenes is a powerful differentiator for WebFOCUS. I believe it's always going to be there.
But will every future feature support it? I guess we will see.