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'm using Report Caster to burst a report to a few email addresses. What happens if the database grows and there's a new value? Can I use some kind of wildcard for the burst value?
I'd like to do one (or both) of two things: 1) Send all burst values to a single email address (even if they aren't known at the time of distribution list generation) 2) Send all unspecified burst values to a default email address
I handled this by bursting my report using a distribution file instead of a distribution list.
I had a FEX that would run prior to my bursted job that would build or modify this distribution file each time my job would run so if there were any burst values in the data but were not in the file it would add it to the file and set the email address to an admin email account so we would know that new values were added in the data but weren't assigned to a specific receipient yet.
By using this distribution file you could also add a default email address for each burst value if you wanted. You can really do a lot of things with it.
Thanks, Jenn
Posts: 22 | Location: Pittsburgh | Registered: December 22, 2003
In 52x, this is even easier. There is a new Dynamic List option that lets you specify a fex that generates the distribution list, and burst values if needed, for the distribution list. It's all covered in the RC Admin guide.
on your wish to 'send all burst values to the same address', you could rerun the job and not burst it, with the same BY field break and just send that output to your one single address. or.. you could run your burst job with CC's; you can specify more than one address for a given burst value. i do that..i have some execs who want their assistants to get copies of their emails, and some who dont. so i justlist the burst value twice in the distlist with two different emails. i didn't see that feature documented, i just disovered it serendipitously
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003