Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] 7.6.10 html painter problems

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] 7.6.10 html painter problems
 Login/Join
 
Gold member
posted
We have a fairly complex html launch page developed in 7.1.7. It has multiple chained list boxes and lots of check boxes. Before we upgraded to 7.6.10, we loaded the html into the painter, changed a new list box properties then ran the process and it worked fine. Problem is, we didn't test enough. After the upgrade, we dropped one of the check box parameters from the fex and removed it from the html. Now the procedure wants to prompt for every check box parameter and we can't seem to figure out how to fix it. We have been over and over the documentation to no avail. I'm guessing we are missing something because surely we are not going to have to rebuild the html process just for 7.6.10.

This message has been edited. Last edited by: Kerry,


Dev Studio /7.6.11/7.7.02M
MVS/USS
AIX/SOLARIS
Windows WF Client 7.6.8/7.6.11
 
Posts: 64 | Location: Eastern and middle NC | Registered: March 13, 2007Report This Post
Virtuoso
posted Hide Post
You may have already done this, but check the Properties for the fex and make sure the Prompt for Parameters box is unchecked. Also, if you don't already have -DEFAULT settings for each of your parameters, adding them should prevent any prompting.


WebFOCUS 7.7.05
 
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007Report This Post
Member
posted Hide Post
We are having the same issues with the new HTML Composer in 7.6.10


Web Focus 7.7.02, Server 2003 64 bit, All output types
 
Posts: 3 | Location: Greeley, CO | Registered: September 17, 2007Report This Post
Gold member
posted Hide Post
It seems that after the upgrade, we are now prompted for any check box that we do not select, even though they all have -DEFAULT values. So, if we don't touch the code, just do the upgrade, this happens.


Dev Studio /7.6.11/7.7.02M
MVS/USS
AIX/SOLARIS
Windows WF Client 7.6.8/7.6.11
 
Posts: 64 | Location: Eastern and middle NC | Registered: March 13, 2007Report This Post
Virtuoso
posted Hide Post
There are a number of parameters that get set up in the WF Client that also control parameter prompting. Did these parameters get set properly when you did your upgrade?


Regards,

Darin



In FOCUS since 1991
WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex
Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex
WF Client: 77 on Linux w/Tomcat
 
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007Report This Post
Gold member
posted Hide Post
Thanks Darin. Not sure. I'll have to forward this to the sys admin that did the upgrade. I just remembered that before the upgrade, we brought up this process in app dev studio 7.6.10, against a 7.6.10 server, then made a change and ran it with no problem. It was only after the official upgrade that this happened which tends to support that there may be an improperly configured setting.


Dev Studio /7.6.11/7.7.02M
MVS/USS
AIX/SOLARIS
Windows WF Client 7.6.8/7.6.11
 
Posts: 64 | Location: Eastern and middle NC | Registered: March 13, 2007Report This Post
Platinum Member
posted Hide Post
Darin,
can you shed a little light on some of those settings? We are currently using 7.6.9 and have encountered a couple of issues and are looking at the "upgrade" to 7.6.10 (soon) for the IE8 capabilities. I have run into some issues with 7.6.9 and the HTML painter. When I try to use a Submit Button in an HTML Painter the Javascript for the button click event does not get placed into the code and I am not sure if version 7.6.10 resolves that issue or not.
Thanks,
EP


WebFOCUS 7.6.9

Reporting client Windows 2003 Service pack 2 using IIS and TomCat 5.5
Reporting Server OS/400 V5R4M0
Outputs: HTML, Excel, PDF, CSV, and Flat Files
 
Posts: 130 | Location: Columbus, Ohio | Registered: February 25, 2009Report This Post
Gold member
posted Hide Post
Because of Darin's note, I went through and checked settings.

During the upgrade to 7.6.10, the property of "Prompt for Parameters" go turned on for all focexecs. Having discovered that, we went through and "unchecked" that property and now the prompting works as designed.

Steve


Dev Studio /7.6.11/7.7.02M
MVS/USS
AIX/SOLARIS
Windows WF Client 7.6.8/7.6.11
 
Posts: 64 | Location: Eastern and middle NC | Registered: March 13, 2007Report This Post
Gold member
posted Hide Post
I know I'm a day late and a dollar short on this, but for the sake of accuracy -DEFAULT does not eliminate prompting of a Parameter, it only loads in a Default value for your parameter. To stop getting prompted for a variable either do a -SET so that the variable is not unresolved or use -DEFAULTH which will hide the default value from prompting, but still allow passed variables to overwrite it.


Eric Woerle
WF 7.6.7 Reportting Server
ETL 7.6.10
Dev Studio 7.6.7
 
Posts: 95 | Registered: July 31, 2007Report This Post
Virtuoso
posted Hide Post
Better late than never, Eric! Your comment was right on the spot and certainly clarifies some confusion surrounding the use of -DEFAULT and its impact on prompting.

Thanks!
Neftali.



Prod/Dev: WF Server 8008/Win 2008 - WF Client 8008/Win 2008 - Dev. Studio: 8008/Windows 7 - DBMS: Oracle 11g Rel 2
Test: Dev. Studio 8008 /Windows 7 (Local) Output:HTML, EXL2K.
 
Posts: 1533 | Registered: August 12, 2005Report This Post
Platinum Member
posted Hide Post
Steve: I will definitely look at all of our Fexes to see if the "Prompt for Parameters" was turned on while we are testing 7.6.10.
Eric: I will have to take a look at the DEFAULTH...I assume that is new to 7.6.10?

When working in the HTML Painter if I add a button to the screen via the GUI and add a hyperlink to the button, should the click event of that button execute to the URL? OR do I need to actually add the JavaScript to the HTML code to add the onclick event for the button? It seems like the program would be intuitive enough to add that on its own but it doesn't seem to be doing that in 7.6.9 or 7.6.10?

Thanks,
Erin


WebFOCUS 7.6.9

Reporting client Windows 2003 Service pack 2 using IIS and TomCat 5.5
Reporting Server OS/400 V5R4M0
Outputs: HTML, Excel, PDF, CSV, and Flat Files
 
Posts: 130 | Location: Columbus, Ohio | Registered: February 25, 2009Report This Post
Expert
posted Hide Post
quote:
Eric: I will have to take a look at the DEFAULTH...I assume that is new to 7.6.10?

This was available starting in 7.6.0.


Ginny
---------------------------------
Prod: WF 7.7.01 Dev: WF 7.6.9-11
Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google
 
Posts: 2723 | Location: Ann Arbor, MI | Registered: April 05, 2006Report This Post
Platinum Member
posted Hide Post
Ginny,
Thanks for the info....My Supervisor let me know that fact about an hour after I posted that question.
Ginny do you know if the Javascript onclick event for a button in the HTML painter gets added automatically when you add the button and reference a URL link within the painter? OR do you have to add the javascript to the HTML code to get the button to work?


WebFOCUS 7.6.9

Reporting client Windows 2003 Service pack 2 using IIS and TomCat 5.5
Reporting Server OS/400 V5R4M0
Outputs: HTML, Excel, PDF, CSV, and Flat Files
 
Posts: 130 | Location: Columbus, Ohio | Registered: February 25, 2009Report This Post
Expert
posted Hide Post
//Begin function button1_OnClick
function button1_OnClick(ctrl) {
// TODO: Add your event handler code here
OnExecute(ctrl)
}
//End function button1_OnClick

This is from an old page I created in 2007 (because I don't do URL references a lot--too much typing) and the button works and runs the focexec. It appears that you don't have to add code to get it to work. I surely didn't.

You could try creating a simple page with just a button and no parms to execute a simple fex just to see what gets generated.


Ginny
---------------------------------
Prod: WF 7.7.01 Dev: WF 7.6.9-11
Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google
 
Posts: 2723 | Location: Ann Arbor, MI | Registered: April 05, 2006Report This Post
Guru
posted Hide Post
quote:
a Submit Button in an HTML Painter the Javascript for the button click event does not get placed into the code and I am not sure if version 7.6.10 resolves that issue or not.


Not sure about 7.6.10, but it is resolved in 7.6.11. Just watch out for PDF outputs, some keywords have new definitions that could change the current layouts. Incorrect HTML calendar dates...


Developer Studio 7.6.11
AS400 - V5R4
HTML,PDF,XLS
 
Posts: 305 | Location: Winnipeg,MB | Registered: May 12, 2008Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] 7.6.10 html painter problems

Copyright © 1996-2020 Information Builders