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 need to know what the correlation is between the email distribution list in report caster and the email addresses listed in the botdest table. We have a web page that allows users to enter the burst values and email address (for distribution) that get inserted into the botdest table. The fex report that is generated, gets scheduled in reportcaster. I want to know if it is necessary to manually enter the email addresses into reportcaster when it is already in the botdest table. How does this work?
BOTDEST is where Report Caster stores the email addresses in distribution lists. So if the addresses are put there by something else, they are "in" report caster.
Do you know if there is any way to filter a report using a where clause in my fex that gets scheduled? I want to be able to filter on a range of values.
Don't know if this is related to your first question or not. And I'm not quite sure what the second question is. Report Caster runs the fex that is scheduled. If there is a WHERE clause in the fex, the data is filtered. If not, there is nothing else in RC that lets you add additional filters.
One way around this (there is always a way around things) that I frequently use when a job is run both on-demand and through RC is the following. I add an additional parm called &RCRUN and use -DEFAULT &RCRUN='N' in the fex. By default, all the code, WHEREs, etc. that will be used ONLY by RC are skipped, branched around, an so on by testing the &RCRUN parm. Then when I set up the job in RC, I add the parameter value of 'Y' to the RCRUN &var under the advanced tab, along with any additional values or ranges of values to be used. If it is run in RC, it uses additional filters. If not in RC, it does not use them.
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