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.
You can set up a "Pre-Process" fex that determines if there is data for the report, if there is no data, set the &&KILL_RPC variable.
Check the ReportCaster Development and Administration manual.
The &&KILL_RPC flag is a ReportCaster amper variable that you can use in a pre-processing procedure when you want to stop ReportCaster processing and not execute the scheduled procedure based on a condition. The condition may be the existence of a data extract, or a restriction on the days that schedules are allowed to run. The code to evaluate the condition can be a combination of Dialogue Manager and FOCUS supported by the WebFOCUS Reporting Server. The &&KILL_RPC amper variable must be set using Dialogue Manager.
How about creating an Alert. I was just going through the manual and looks like creating an alert would be a good thing for that. The manual only tells the procedure how to create the alert, no example code to go through. I have to play with it and see how it works.
Would someone post the sample code of how to create an alert
easier.... Do your Fex in 2 steps. 1) create the exact hold file from which the report would be created. 2) test the &LINES variable for value if &LINES EQ 0 GOTO ENDOFJOB; 3) table file hold write your nice report
This is easy and works like a charm. I do it 8zillion times a day. If there is no data, the fex bypasses the nice fancy html report generator; If there is no html output, the RC log will show NO REPORT TO DISTRIBUTE and nothing goes to anybody. ok ok...it was 3 steps.
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003