Document definitions based on StoryTeller templates In this scenario, a Telecom company has decided to use Composition Center to generate printed invoices. Andrew is a document designer, in charge of the corporate graphical profile. He is responsible for designing the invoice layout. Andrew uses StoryTeller to define the pages and to add content, such as the corporate logotype, and fields for customer name and address, invoice number, due date, etc. He also designs a table for recurring data and adds a text object intended for campaign messages. On the back of the invoice he adds a text object intended for terms of payment. When Andrew is finished with the layout, he exports the layout and sends the file to the document developer Diana. Diana is an OpenText consultant at Telecom, and is responsible for integrating the invoice layout into a Design Center Project. She imports the layout file into a StoryTeller Process, and binds data to the fields and the table intended for recurring data. To reference the campaign message and the terms of payment, she inserts sections into the text objects. When she is finished she exports and deploys the Project and starts the StreamServer application. Now a template for invoices is available in Composition Center and Diana notifies Mary at the legal department. Mary is a business user with approval rights in Composition Center. She has written and approved the text regarding terms of payment in Composition Center and the marketing department has designed two different campaign messages intended for different customer categories. After being notified by Diana, Mary logs in to Composition Center and creates a document definition using the invoice template. She adds the campaign messages and sets rules to control which one to use depending on the customer category. She also adds a rule to control when invoices are generated and on the back she adds the terms of payment. Finally, Mary previews the document and since she is pleased with the result she publishes the invoice. When the document definition is published, its content and rules are made available to the StreamServer application. When the rule for the document definition is fulfilled, the StreamServer application uses the document definition to generate invoices. The rules set on the campaign messages controls which message that is used.