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.
the 1,2 are the choices that a user will see in the dropdown box. You would put there what you wanted to offer the user as valid selections such chalk,cheese
I am quite aware of how to deal with IF or WHERE clauses in a TABLE request.
My question is with ergard to the extensions to traditional autoprompt syntax when Dialog Manager variables appear in Focus statements: is there a semantic difference between &foo.(OR(a,b,c)).Choose your FOOs. and &foo.(AND(a,b,c)).Choose your FOOs. ? Other questions:
- Does the -DEFAULT feature apply to "multiple" selects, or only "singles".
- How does execution proceed? Clearly the agent must first parse the fex, recognize that there is auto-prompt syntax, and return a form. Since agents operate nonpersistently, the form has to re-invoke the fex upon submit. How does the second call make it clear that it is not a first call? How is the context preserved and restored (e.g., if the fex was originally called with some &vars set; or if there are && global vars set)?
- Note that autoprompt occurs even for &vars with -DEFAULT values supplied -- even though, in traditional Focus and WebFocus fex execution, they would not be considered undefined.
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
I did not mean to imply that you did not understand standard logic. I merely wanted to give a fuller explanation for those who have less understanding of what we are talking about.
The semantic difference for OR/AND is purely the operand that you choose.
The wrong one, it does not work the correct one and it does.
Execution is very simple,
The first request is EX FEX
The second request is EX FEX var1=xx,var2=yy
WebFocus Knows that when variables have a value it does not need to prompt for them.
You can test this by creating a report with an auto prompt but supply the required variable name and value on the input line in a browser. Supply the value and it will not ask you for it.
Auto prompt when enabled disables �DEFAULT, because Auto prompt means give me a value. Personally I think that this is wrong and it should say if you haven�t given me a value I�ll use the �DEFAULT instead. Perhaps an NFR is required.
[qb] WebFocus Knows that when variables have a value it does not need to prompt for them.[/qb]
A -SET value, as distinct from a -DEFAULT one. (They are distinguishable.) As I noted, that varies from traditional autoprompting rules.
[qb]... Auto prompt when enabled disables �DEFAULT...[/qb]
I didn't see that in the cited document for self-service apps. In fact, I didn't see any way to turn autoprompt off. -- By its nature it would have to be a DM directive, since this all happens before -RUN.
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005