So what should a good solution look like?
- It should have a sophisticated templating environment, suitable for use by a wide variety of users.
- Data and presentation should be separated, so that the presentation (e.g. how the document looks) should be able to be changed independently from the system(s) that produces the data – i.e. you should be able to change the content and styling of a produced document, without modifying the core system.
- Changes should be able to be made quickly and with confidence.
- Content should be re-usable across the enterprise.
- The solution should be standards based.
- The solution should have an open architecture.
- The solution should provide services suitable for consumption in an SOA.
- The solution should be performant enough to support the enterprise.
- The solution should be architected in such a way that it can be easily integrated into existing processes, data providers, and workflows.
- It should be capable of providing a large number of output formats.
- The content should be secure.
The following diagram illustrates a best-of-breed approach using the Scriptura Engage product set.
It is important to note the following:
- More than one calling application uses the same document generation service. Note that in this case the interface to Scriptura, is via web-services.
- The templating tool is the same for each calling application, allowing for the duplication and centralization of templating resources.
- The server can produce multiple output formats.
For more information please contact us.