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.
There are no defaults. ( we don't need/use them... )
usually we do it like this:
-SET &WHERE_CUSTOMER_ID = IF &CUSTOMER_ID EQ '' OR ' ' THEN '' ELSE 'WHERE CUSTOMER_ID EQ ' | CUSTOMER_ID;
remember, it does work on the current environment.
Yes, I've relinked it... ...and even made a complete new fex & html on the new server.
same problem.
...wasn't that -default stuff an issue with upgrade to WF8? ( which we're planning too ). I vaguely remember now there might be an hotfix difference between the current and the new server.
_____________________ WF: 8.0.0.9 > going 8.2.0.5
Posts: 668 | Location: Veghel, The Netherlands | Registered: February 16, 2010
I don't know why it was working before for you, but for me the autoprompt still shows up if you give the user the no selection option but don't use default.
WebFOCUS 7.7.03/8.0.08 Dev Studio 7.7.03/8.0.08 App Studio 8.0.08 Windows 7 ALL Outputs
Posts: 402 | Location: Upland, IN | Registered: June 08, 2012
Maybe "In the new situation" the handling of blank values has changed, and your blank parameters are no longer included in the call.
As I understand it, the autoprompt comes up after the UI calls the fex. The Lord High Executioner prescans the fex, and compares the set of passed parameters with the list of uninitialized &vars referenced in the fex. If any referenced &vars that are not previously assigned a value (by -SET or -DEFAULT/DEFAULTH) in the fex, are not received as parameters, they go into the autoprompt list. If the autoprompt list is populated, EDA presents an autoprompt page, rigged beneath the sheets so that it will pass the original request PLUS any new parameters supplied via autoprompt.
If your UI page unfailingly passes the parameter (whether blank or otherwise), then
-DEFAULT &CUSTOMER_ID = '';
(or -DEFAULTH) is harmless.
On the other hand, if the parameter is omitted when its value is blank, the -DEFAULT is appropriate and will save the day.
- Jack Gross WF through 8.1.05
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
And what I don't understand. If a parameter is passed from the HTML to the fex, even left empty, it STILL exists. Being an empty string ''.
The mapping of parameter phrases in the url ("...&alpha=FOO&beta=&gamma=BAR") to Focus &vars does not happen by itself, it's the responsibility* of the "CGI" piece in the "client" -- so how it reacts to an empty parameter (&beta=&) -- whether or not it sets &beta=''; -- might be inconsistent. Shouldn't be, but ....
*and it's not precisely one-for-one. For instance, generates "indexed" vars when it encounters duplicate parm names ( mapping P=abc&P=def to &P1='abc'; &P2='def'; &P0=2; ) and it treats some parameters as execution directives rather than application dataThis message has been edited. Last edited by: j.gross,
- Jack Gross WF through 8.1.05
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
I heard that when you have the message viewer on (selected) on the run button in DevStudio and you have autoprompt setting on this may occur. Something to check - hit the down arrow on the run button in DevStudio and select "Message Viewer OFF".
Hope that helps!!! Barry
WebFOCUS 8103, Windows, App Studio
Posts: 80 | Location: NYC | Registered: November 13, 2008
Did IBL/NL identify the nature of the failure in pre-HF5 JavaScript files? Have they delineated the circumstance that results in the unwarranted autoprompting?
AFAIK, the decision whether to issue an autoprompt screen occurs on the server, so how does JavaScript (executed in the browser) come into play?
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
I don't know the details. Our admin had contact. All I know they said to replace a .js with the same one from the 'other' server with the previous version.
Might be something the HTML page does with 'empty' parameters. ( on the user browser ).
Greets,Dave
_____________________ WF: 8.0.0.9 > going 8.2.0.5
Posts: 668 | Location: Veghel, The Netherlands | Registered: February 16, 2010
The javascript interprets the IBI xml stuff at the bottom of the launch page and is for a large part responsible of what gets sent from the launch page to the server. For example, this might well have to do with the introduction (and default to) the _FOC_NULL value.
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
Is your autoprompting set to the default XMLPROMPT (which prompts even when there is a -DEFAULT, apparently) or to the less intrusive XMLRUN?
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
Which was fine in 7702B and with the above fix also in 7702D.
We do stuff like this:
-SET &DYN_WHERE = IF &UI_FILTER EQ '' OR ' ' THEN '' ELSE 'WHERE SEATS EQ ' | &UI_FILTER;
TABLE FILE CAR
SUM SALES
BY CAR
&DYN_WHERE
END
We did it this way so the user may leave unused filters ( inputboxes ) empty.
....and yes, we know all kind of workarounds. It's just that a big part of our fexi are designed this way. It would be a **** of a job to rewrite all the code just because WF8 doesn't support something that was fine in WF7.
And it isn't even code-thightning. ( I'm logging those to help all you guys planning to migrate to WF8 ;-) )
Greets,dave
update: 100 points for the one who knows which, obviously unbelievable rude word, I used that was automatically replace with ****
_____________________ WF: 8.0.0.9 > going 8.2.0.5
Posts: 668 | Location: Veghel, The Netherlands | Registered: February 16, 2010
Hi Dave, It is a colossal pain. It is code-tightening, and, IBI now prompts for any variables, as well as, those that are generated via the form, i.e., check the box to Send Display Value to use in a Parameter sheet for Excel output, 9 out of 10 times, the autoprompter would pop-up with NO variables to enter, so, we had to search and guess why. Because of this, it's taken over a year to convert from WF7 self-serve to WF8 Content/MRE...
Thank's for letting me vent, it's been a long year...This message has been edited. Last edited by: Tom Flynn,
We initially went to 8.04, then 05, now we are on 07 and waiting for 8.1. Convinced the client not to upgrade any further until things got sorted out. Sounds like IBI may have relaxed the ampere variable issues with 08 and up, but, really don't know...
BTW, if you have InfoAssist, must have the setting set to XMLRUN, we had it OFF in self-serve. Our fix was to use -DEFAULTS, then change the ones that are not on the form to -DEFAULTHThis message has been edited. Last edited by: Tom Flynn,