Report Information

After you have specified scheduling options, you must specify the Report Information.

The following image shows the Report Information window, which is where you specify the report format, whether to enable report bursting, and the Execution ID and password that is authorized to execute procedures on the server running the report.

Top of page

Procedure: How to Specify Report Information Options

Specify the following report information:

From the Report Format drop-down list, select the report format. HTML is the default value.
There are limitations on what formats are valid for certain options. Not all formats are supported for bursting or for printing. If the report format statement in the coded procedure is a styled report format, then you must select a styled report format (for example, AHTML, EXL2K, EXL97, HTML, PDF, PPT, PS). The report format specified in this field overrides the format statement in the procedure.

If the report format statement in the coded procedure is a specialized report format such as EXL2K FORMULA, EXL2K PIVOT, EXL2K TEMPLATE, PPT TEMPLATE, or if it is Coordinated Compound PDF Report, it is required that you select the same report format that is specified in the procedure.

If a TABLE request containing an unstyled binary format (for example, EXCEL and WK1) is scheduled for distribution as a styled ASCII format (for example, EXL2K, HTML, PDF, or PS), the report is not created by the WebFOCUS Reporting Server and the ReportCaster log report contains a "No destination found for this distribution" message. This also occurs if a TABLE request containing a styled ASCII format is scheduled for distribution as an unstyled binary format.

The report formats that appear in the Scheduling Wizard are configurable using the ReportCaster Server Configuration tool. If you want the Scheduling Wizard to display different report formats, contact your ReportCaster Administrator.

For detailed information about each format, see ReportCaster Formats for Scheduled Output.
Optionally, if you want to burst the report, select the Enable Report Bursting check box. The burst feature enables you to break a report into sections and distribute the sections separately. Burst values may be specified in a Distribution List or Distribution File. For more information about bursting, see Bursting Guidelines and Limitations, and Bursting a Report.
Specify an Execution ID that is authorized to execute procedures on the server running the report.
- If the Execution ID field is not grayed out, and you are using an Execution ID that you previously used for a schedule, select the Choose Security Information option button. Next, select the Execution ID from the drop-down list.
  For example, the following image shows the rcuser Execution ID selected in the Security Information pane.
- If the Execution ID field is not grayed out, and you are using a new Execution ID, select the Enter the Execution Id and Password that will be used to connect to the WebFOCUS Reporting Server option button. Next, type the Execution ID and password in the appropriate text boxes.
  Note: The Execution ID is added to the ReportCaster Repository and is viewable in the ReportCaster HTML User Interface.

Click Next on the bottom of the Report Information window to continue scheduling the report:
- If the report you are scheduling has parameters, you are sent to the optional Report Parameters window. For more information, see Report Parameters.
- If the report you are scheduling does not have parameters, you are sent to the Distribution window. For more information, see Distribution Options.

Top of page

Bursting Guidelines and Limitations

Bursting enables you to target relevant sections of a report to individual users. Each section is saved as a separate file. If you are distributing a burst tabular report, the burst value is determined by the first BY field. If you are distributing a burst graph report, the burst value is determined by the second BY field. The burst value is automatically determined by the internal matrix of the WebFOCUS Reporting Server. The internal matrix is a memory area that stores each database field value and calculates values referenced by the TABLE or GRAPH request.

When a report is burst, all data values generated for each burst section are returned to the ReportCaster Distribution Server.

For the Managed Reporting and Library distribution methods, each burst section is distributed to Managed Reporting or the Report Library. Each burst section may be viewed by the owner of the schedule. Library user access to burst report sections is restricted as per the authorization (owner, public, access list) specified in the schedule information and Managed Reporting security if the scheduled report is a Managed Reporting procedure.
For the e-mail and printer distribution methods, specific burst sections are distributed based on the burst values specified when creating the Distribution List, Distribution File, single location, or dynamic address list used by the schedule.

The following are guidelines and limitations that apply to the ReportCaster burst feature:

Case. Burst values are case-sensitive.

Keywords. Burst values can contain the following keywords:

Wildcard Characters. Use an asterisk (*) and a question mark (?) as wildcards to represent characters at the beginning, end, or middle of the burst values. The asterisk represents one or more characters, while the question mark represents any single character. Precede each instance of a burst value using a wildcard with the wildcard keyword enclosed in brackets followed by a colon, [wildcard]:, as shown in the following examples.
[wildcard]:abc* = all values that start with ‘abc’.

[wildcard]:a?c = all three-character values that start with ‘a’ and end with ‘c’.

[wildcard]:a?c* = all values that start with ‘a’ and have a ‘c’ as the third character.
Java Regular Expressions. Use to identify strings of text. Precede each instance of a burst value using a Java regular expression with the regular expression keyword enclosed in brackets followed by a colon, [regexp]:, as shown in the following examples.
[regexp]:[bcr]at = values that are bat, cat, or rat.

[regexp]:[^bcr]at = any value that is not bat, cat, or rat.
Default Distribution. You can provide a default destination for burst values that are not specified in the Distribution List. To do this, enter the following in the burst value column of the Distribution List.
[elsesend] = reports for burst values not contained in the Distribution List will be sent to the named recipient.

The following are example entries in an e‑mail distribution list that illustrate the use of the wildcard and default distribution keywords in burst values.

Burst Value	Address
[wildcard]:an	sml@company.com
England	ray@company.com
[elsesend]:	jt@company.com

Using a scenario where the report is burst on the Country field that contains values of Germany, USA, France, Canada, Italy, Chile, England, and Japan, then:

report information for Germany, France, Canada, England, and Japan will be delivered to sml@company.com
report information for England will be delivered to ray@company.com
report information for USA, Italy, and Chile will be delivered to jt@company.com

Formats. AHTML, DOC, EXL2K, EXL97, EXL2K FORMULA, GIF, HTML, JPG, DHTML, PDF, PNG, PPT, PS, SVG, and WP support bursting. Each burst section of the report will be named burstvalue.format (for example, Northeast.pdf).

ACROSS command. This command is not evaluated as a primary sort field. To burst a report, you must also include a BY field. Bursting occurs on the BY field.

FML reports. Bursting an FML report is supported only if the request has a BY field.

Coordinated Compound Reports. ReportCaster can burst and distribute coordinated compound reports developed using the Document Composer in Developer Studio in DHTML, PDF, and PPT formats. Compound reports that are not coordinated cannot be burst.

TABLEF. No internal sort processing is performed. The specification of a BY field requires that the data already be sorted in the data source.

ON TABLE SUBHEAD/ON TABLE SUBFOOT. Creates a SUBHEAD for only the first page of the report, and a SUBFOOT for only the last page of the report. When bursting a report, the SUBHEAD and SUBFOOT should occur for each sort break. Therefore, specify the primary sort field in place of TABLE in the ON command. For example:

ON primarysortfield SUBHEAD

AnV field types. Bursting is not supported on a field with the AnV (where n is an integer value) field type.

Note: For additional considerations when using WebFOCUS commands with burst reports, see Using WebFOCUS Commands With Burst Reports.