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 am trying to create a scheduled task that would send several Excel files based on one fex file. The Excel files would be separated by customer. For example, a user would get an email with 3 attachments that contain data for customer 1, 2 & 3 with each customer number being in there own Excel file. I tried using PAGE-BREAK but that didn't work. Using a compound document with OPEN, CLOSE will not work because they will all be in the same Excel file. Any ideas?This message has been edited. Last edited by: <Emily McAllister>,
Unfortunately, up to WF 8.0.08 it just simply is not possible. I don't know if newer versions allow this but I think it's highly unlikely, since practicality is not a WebFOCUS strong suit. Each task can only create one attachment.
One workaround I can think of is to use BYTOC to split each customer to separate tabs:
TABLE FILE CAR
SUM
SALES
BY COUNTRY
ON TABLE PCHOLD FORMAT EXL2K BYTOC
END
This does not sound like it will help you, but in one schedule, you can have more than one task - each task will create its own attachment...
I stand corrected.This message has been edited. Last edited by: Francis Mariani,
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
I have it with a sales report per profit center/selling branch where each profit center numbers are sent in a separate Excel file to specific people and some receive more than one file as attachment.
Sample
-* File SAMPLE_BURSTING.fex
DEFINE FILE CAR
BYSEQ /P2 = DECODE COUNTRY ('FRANCE' 1 'ITALY' 2 'W GERMANY' 3 'JAPAN' 4 'ENGLAND' 5);
END
TABLE FILE CAR
SUM SEATS
RETAIL_COST
BY BYSEQ NOPRINT
BY COUNTRY
BY CAR
BY MODEL
ON TABLE PCHOLD FORMAT EXL2K
END
-RUN
Then create a schedule with the "Burst Report" option checked, have a distribution list where you list the different burst values (BYSEQ) with their corresponding e-mail address.
If you put your e-mail for all 5 values, you will receive one e-mail with 5 attachment.This message has been edited. Last edited by: MartinY,
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
Unfortunately, Francis that wouldn't work. Those tabs need to be in their own separate Excel spreadsheets. I know this specific operation is possible, because we had a scheduled task in ReportCaster that would accomplish this, but then an error occurred and it hasn't worked since. I checked the scheduled email task and fex code and there is nothing that would show separate Excel files being created. There is a PAGE-BREAK, but that only seperates the customers into separate sections on the same Excel file and same sheet.
What code did you use, Martin, to accomplish this?
Here is a sample of the messages in the log report...
Job started running at 2016-05-24... Job remained in queue for .0010 seconds. Starting Task: Task 1 - Customer Bakery. Task Type: EDA RPC. Procedure name: blah blah... Connecting to server blahblah with execution id admin... Executing focexec. Connection to reporting server closed. JOb ran on the reporting server for 2.343 seconds. Task finished. Starting Task: Task 2 - Customer Supply.
And relatively similar messages follow after every task.