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     [CASE OPENED]Passed 'empty/null' value not captured in HTML Composer file

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CASE OPENED]Passed 'empty/null' value not captured in HTML Composer file
 Login/Join
 
Silver Member
posted
Can/Would anyone kindly provide insight about whether the below behavior is intended..or if it is an 'undocumented feature'??

When an HTML form, created in WF8 composer in App Studio, sends a blank value (ie '' or no entry/value) to a fex, thru an input/text box, the fex is promopting for the empty parameter.

If the form sends a actual space value (ie ' '), then the fex runs properly.

On the WF client, the IBI_WFDescribe_Default = OFF for Parameter Prompting.

Additionally,
1. When the report is run by itself, and that paramer is set like these below....then there is 'no prompting'.

-SET &STORE = '';
-TYPE &STORE
NO Prompting.

-SET &STORE = ' ';
-TYPE &STORE
NO Prompting.

I think this is a new behavior w/ WF8. I remember that, in previous releases, a null/blank was respected and passed thru the Servlet as a an empty space.

And..I don't think this is behavior at the reporting server layer..I think it is when the HTML form is being parsed for execution.

The implications of this is that, during our upgrade to WF8, we have hundreds of fexes which recognize a '' value for a parameter...and the report behaving a certain way. We don't want to have to come up w/ a form/fex hack (like a -DEFAULT &PARAMn = ''Wink

Any insights would be greatly appreciated.

Wm

This message has been edited. Last edited by: <Emily McAllister>,


WebFOCUS 8
Windows, All Outputs
 
Posts: 30 | Location: Living in Charlotte, working all over | Registered: July 13, 2015Report This Post
Silver Member
posted Hide Post
Turn off the 'prompt for parameters' property on the fex, and the html page will not reprompt for null parameters.


WF 8.1.05 on Windows machines
Backend: Informix, SQL and Oracle databases
 
Posts: 37 | Location: Houston, Texas | Registered: May 01, 2008Report This Post
Silver Member
posted Hide Post
Thanks for that suggestion...I tried that..Unfortunately, it had not affect.
The 'prompt' HTML page still appeared to prompt for the null filled parameter/variable.

I'm going to open a case w/ IBI.

thanks


WebFOCUS 8
Windows, All Outputs
 
Posts: 30 | Location: Living in Charlotte, working all over | Registered: July 13, 2015Report 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     [CASE OPENED]Passed 'empty/null' value not captured in HTML Composer file

Copyright © 1996-2020 Information Builders