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 been trying to start using parameters in my procedures. I am getting the FOC295 error:
(FOC295) A VALUE IS MISSING FOR: &DATESTATUSCHT
I read one thing that said Parameter Prompting needs to be activated on the reporting server client config.
As of right know I have been told that it cannot be turned on.
I there some kind of workaround for this? Here is my code.
JOIN CLEAR * DEFINE FILE LCCCCC END TABLE FILE LCCCCC PRINT PO FACEAMOUNT AS 'FACE,AMOUNT' STATUSCODE ISSUEDATE BY HIGHEST DATESTATUSCH NOPRINT WHERE DATESTATUSCH GE '&DATESTATUSCHT.Pleas enter a date (ex. 1990204).'; ON TABLE SET PAGE-NUM OFF ON TABLE NOTOTAL ON TABLE PCHOLD FORMAT PDF ON TABLE SET STYLE * UNITS=IN,
Thanks
DanThis message has been edited. Last edited by: moyer1dl,
There are generally speaking two ways to provide parameter values. The first is indeed by activating the parameter prompting. But since that is not possible or allowed right now, there is only the other way left. And that is by creating a piece of front end code that will ask for parameter values and transport them back to your fex. Either create your own html file manually or use the html painter built into devstudio to define and handle the fields. Remeber that each html-field will become an &-var in your fex...
Hope this helps ...
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
I am running through Dev Studio. I run remotely off the Mainframe and am reporting of off SQl databases. We do not have the MRE. My goal is to start making Self service start up pages to get away from running from the FEXs and have more user input instead of hard coding parameters.
GamP, do you have any samples or links on how to do this in HTML?
You're using DevStudio - so go to your app folder, open the html folder, and create a new html file. Be sure to base this on your fex. In html painter: create a New Report, place it somewhere on the page, right click on it and say 'Import existing proccedure'. Then select your fex, and basically you're done.
Start playing around with it, it really is a nice tool (for a start).
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
The HTML painter utilizes parameter prompting from a fex - meaning that it will read the fex and put any unresolved parameters on the html page as input elements.
Your very first post was about Autoprompting. Which is basically the same only now at runtime, not at development time. If autoprompt is not active, you'll get the error that you experienced. But html painter will still work and will still give you all unresolved &vars as input elemenets.
And, I have to admit, I never even looked at the tutorial....
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007