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 a sql statement in a foc exec that upon completion executes another foc exec. Works great for SQL that doesn't have user inputed parameters. But for the ones that require user input parameters i would like it to run the sql and clear the parameter inputs off the screen before running the next FEX i want to call. I'm sure there is a focus command to do this but i can't seem to find it. Any help would be appreciated.
Thanks
Here is an example -SET &AGENT_USER = GETUSER('A30'); ENGINE SQLORA SET DEFAULT_CONNECTION ismd01 SQL SQLORA INSERT INTO PARTNER (IDPARTNER, BUNAME, NAME, SITECODE, UPDATEUSER, UPDATEDT) VALUES ((SELECT MAX(IDPARTNER)+1 FROM PARTNER), '&Partner', '&Client_Number', '&Client_Number', '&AGENT_USER', (SELECT SYSTIMESTAMP FROM dual)); END EX app/list_partners.fexThis message has been edited. Last edited by: Kerry,
I'm a bit uncertain as to what exactly it is what you want/need. You talk about clearing variables. But when you do an EX, all single &variables will not be available to the procedure being EXed. So setting them to space or whatever has no influence.
You also say
quote:
But for the ones that require user input parameters i would like it to run the sql and clear the parameter inputs off the screen before running the next FEX i want to call.
Not quite certain what you mean with this.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
I too am not quite understanding what you need. A single form submits a single job/fex. When that fex completes, it creates the output somewhere (on disk or back to the browser/client.) At that point, it's done. There is no stopping in between procedures to request additional parameters. And there is no communication back to the submitting form to clear values or to submit another fex. It just returns the answer set or processing completed message.
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, 2007
Let me see if i can clarify this. I have a report that shows a list of people. The data in this column has a drilldown to a target=_self focexec that is called Add a customer. It passes no fields but the sql focexec it calls looks for a paramter field for the name of the person you want to add. Hence you get the parameter input. You enter the persons name and click run and you get the message 1 row added to the database. If I put the ex list_people at the end it adds the person and runs the report but i still have the parameter input fields used for the sql above the report. What i'm trying to accomplish is you enter the name press run to execute the sql runs and the report runs but clears the original paramater input for the sql off the screen. So it looks like you brought up the list of people with the new person you just added without the parameter input request that was needed for the sql to execute.