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.
In there an area in InfoAssist where I can turn SET commands on or off? I am trying to turn CENT-ZERO on.This message has been edited. Last edited by: <Kathryn Henning>,
There is no specific area in InfoAssist where you can turn SET commands (yet). What you can do is create a Preprocessing Other component in a Reporting Object and type in all the SET commands there. Then you would invoke InfoAssist from the Reporting Object and SET commands would be initiated.
Would you recommend Reporting Objects or Synonyms for end users to use as data sources when working with InfoAssist?
I had never given Reporting Objects a big thought but now that we're working on a proof-of-concept for InfoAssist we've noticed that Reporting Objects really come in handy on certain circumstances:
- Allowing to execute SET commands applicable only to InfoAssist reports derived from the object (CENT-ZERO, COUNTWIDTH, LINES, etc.) - Establish the default data source along with whichever valid joins that may be needed, relieving the users from having to join sources themselves - Define filters that can be enabled/disabled by the user - Provide a "start version" of a report or graph so users will have something to run by default
and...NewJersey...Buidling a Business View, a somewhat fancier version of an RO, lets you build a large masterfile out of all the masters of a joined entity, then comment out the fields you don't want your users to see (or have to deal with), and defining variables (such as counters) at the level that is appropriate . Business Views rock.
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
Yup, that's exactly the combination I have. We've created a few Business Views joining our main Facts to Dimensions and look up tables, grouping fields in "logical folders" with business some meaning and hiding those fields that we don't want exposed.
However, we encountered additional value in building Reporting Objects on top of those Business views due to the reasons I exposed above (default SETttins, Filters and start-up report layout) and the combination is proving to be quite effective so far