Reports can be combined to form larger packets, which are called bundles. This bundling is possible even if the reports come from different data sources. The reports grouped in a bundle are processed together as a unit.

In a bundle definition, you specify which reports are to be part of the bundle. When an active report assigned to a bundle is processed, Entire Output Management creates an active bundle based on the bundle definition.

To define a bundle, you create a bundle definition, consisting of various attributes which control the processing of the bundle:

• General attributes determine the retention period of the bundle, the reports which trigger the printing of the bundle, and a few other settings.

• Schedule attributes determine when the bundle is printed.

• Printing attributes determine on which output device the bundle is printed, and which separator pages are printed at the beginning and the end of the bundle, and between the reports in the bundle.

The printing of a bundle can be triggered:

• manually by an authorized user;

• automatically at a predefined time, as specified in the schedule attributes;

• by the creation of one or more active reports which are part of the bundle;

• by an Entire Operations trigger;

• by an API trigger from an external application.

A table of contents is always printed at the beginning of the bundle, listing the reports it contains.