|
Trend: Separate Layout and Content A letter consists of two parts: what should be printed in the letter (content), and how the content has to be formatted (layout). Today, we all agree that these are two separate issues, but in existing solutions it is often still the case that for each letter a dataset (query or selection of data), and a layout must be defined. Modifying the content often means that the layout also needs to be adjusted. In some cases this may mean that if you, for example, want to print a customer number on your dunning letter, you have to make this adjustment for each type of dunning letter (reminder, 1st dunning letter, 2nd dunning letter, if any, multilingual). Or what if you want a different logo on your letters? You must modify all your letters. Within Letter Content Management we do this differently. Read more about this in the Datasheets about Bridging Letter Content Management. |
|
Bridging Letter Content Management Bridging Letter Content Management allows you to quickly, easily and professionally develop and maintain documents from the Oracle e-Business Suite, without any technical support. |
|
Create and Maintain Documents Although the sending of letters and the creation of documents, is one of the most important functionalities that an application should support, the definition of a letter, and above all how to customize an existing document often requires a lot of time and technical knowledge, which results in high costs and long lead times. Next to that, you often depend on external parties, because you do not have the technical knowledge. Letter Content Management, enables you by functional setup only to define and maintain documents and send these as XML or print as PDF. |
|
Datasheets |
|
© Bridging 2009. Last update: 3 September 2010 |
