text: Documents are identified (indexed) by date, with one or more other fields, such as customer 
  name, customer number, or invoice number. A date is optional but highly recommended for 
  optimizing document search performance. 
  
  Our example fictitious company, AFinancial Co, prints customer credit card statements 
  monthly. This report, the customer credit card statements (Customer Statements), consists of 
  thousands of individual customer statements. The company also prints transaction logs 
  monthly. This second report, the transaction log (Transaction Report), contains thousands of 
  customer transactions per month. The company must load these two reports into Content 
  Manager OnDemand so that their data can be stored, then easily searched, retrieved, and 
  viewed later. Let us look at how these two large reports might be broken up into individual 
  Content Manager OnDemand documents. 
  
  Reports are “loaded” into the Content Manager OnDemand system. A Content Manager 
  OnDemand application describes how the report will be divided into documents. Figure 1-2 
  on page 8 illustrates two reports, their associated Content Manager OnDemand applications, 
  and documents. Let us look at how the associated applications divide the reports into Content 
  Manager OnDemand documents. 
  
  The first report that we look at is the Customer Statements report. For this example, the 
  report consists of 63,097 individual customer statements. An administrator can define a 
  “*Statement application*” for this report that breaks up the report into logical documents. The 
  Statement application uses the document indexing method to divide the report into 
  documents that are based on customer name or customer number. Each statement in the 
  report becomes a document in Content Manager OnDemand. Users can retrieve a statement 
  by specifying the date and any combination of customer name and number. 