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 looked in the manual and there is only documentation for positional parameters i.e.,it has to be passed in the order of var1, var2 ,etc without specifying the variable name. For Ex: SQL MSS EX TEST 1,0,'a' But our requirement is that these stored procedures change and new variables might get added in the middle.., so we need to reference them using their name, so that we do not have to change the code.
App Studio Version 8202 windows Platform SQL Server 2008/2012
Posts: 183 | Location: TX | Registered: January 22, 2007
,it has to be passed in the order of var1, var2 ,etc without specifying the variable name.
Sadly there's your answer from a WF rule standpoint.
If you really want to pass just 2 or 3 parameters to your 10 parameter stored procedure, you may need to create a "helper" or wrapper stored procedure that *always* receives the 2 or 3 parameters you would pass from WebFOCUS. From within that procedure, you can then call your other stored procedure specifying only the parameters you want by name (not by position).
Of course, that means that if you envision having different WebFOCUS "ways" to call your stored procedure, then you'll need as many wrappers. Not optimal but it's the only way I can see to not be limited by the WebFOCUS syntax.
Let's hear from others suggesting something more workable and maintainable.This message has been edited. Last edited by: njsden,