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.
New TIBCO Community Coming Soon
In early summer, TIBCO plans to launch a new community—with a new user experience, enhanced search, and expanded capabilities for member engagement with answers and discussions! In advance of that, the current myibi community will be retired on April 30. We will continue to provide updates here on both the retirement of myibi and the new community launch.
What You Need to Know about Our New Community
We value the wealth of knowledge and engagement shared by community members and hope the new community will continue cultivating networking, knowledge sharing, and discussion.
During the transition period, from April 20th until the new community is launched this summer, myibi users should access the TIBCO WebFOCUS page to engage.
The following code models a report we'd like to schedule in ReportCaster:
-* File BurstByEmail.fex
DEFINE FILE GGSALES
EMAILADDRESS/A50 = DECODE REGION ('Midwest' 'email@example.com'
TABLE FILE GGSALES
BY EMAILADDRESS AS 'Email Address'
ON EMAILADDRESS PAGE-BREAK AND REPAGE
IF REGION EQ 'Midwest' OR 'West'
ON TABLE SET STYLE *
INCLUDE = endeflt, $
The scenario is that one TABLE FILE command will crank out a report sorted by email address (a person).
We would like the schedule this job in ReportCaster and have RC burst the report by email address, and send out the report to the email address for that page/section of the report.
We've only begun to use RC, and at this point we've only been sending out a specific report to a specific email address. (This has been working great! :-))
This is the first time we are attempting to burst.
The email addresses found and displayed by the report can vary. It wouldn't ever necessarily be the same person(s). (In other words there isn't a 'distribution list'.)
Any/all assistance gratefully accepted.This message has been edited. Last edited by: David Briars,
Pilot: WebFOCUS 8.2.06 Test: WebFOCUS 8.1.05M Prod: WebFOCUS 8.1.05M Server: Windows Server 2016/Tomcat Standalone Workstation: Windows 10/IE11+Edge Database: Oracle 12c, Netezza, & MS SQL Server 2019 Output: AHTML/XLSX/HTML/PDF/JSCHART Tools: WFDS, Repository Content, BI Portal Designer & ReportCaster
We used a Distribution File for the distribution type and created the distribution file dynamically with a pre-processing fex in the RC job. The pre-processing fex reads from a SQL view that stores everyone’s email addresses by division name. The records in this view, and therefore the resultant distribution file, contained many records similar to this; John.Doe.@whatever.org;Jane.Doe@whatever.org,SALES,$
The main RC fex then uses SALES as the first BY field. The pre-processing fex must reside on the reporting server but it’s all detailed in the RC manual.
A Dynamic Distribution List enables you to return in memory either a list of burst values and destinations, or only a list of destinations from a data source (for example, a flat file, SQL database, FOCUS data source, or LDAP).
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
Yes, Value and Dest, which must match the primary sort order in the fex to be bursted when using a Dynamic Distibution list (DDL). Execute a fex within the RC job from the content folder and select the the DDL from a fex from the app folder for your RC job. Enjoy It!
In FOCUS Since 1983 ~ from FOCUS to WebFOCUS. Current: WebFOCUS Administrator at FIS Worldpay | 8204, 8206
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005