Building a Document Framework
The Developer Role
To define a new document application a user
authorized as developer can create new document
elements which are later formatted into the
final document. The developer creates the
document frame, class or type and defines
how the business data is to be interfaced
with.
To interface with business data either a
Papyrus Type Manager for i.e. DB/2 or Oracle
is used or Papyrus interfaces through standard
Adapters to messaging systems such as MQ
Series and business systems such as SAP,
CICS, IMS and others. Adapters enable also
easy integration with all legacy systems.
The developer has access to the Papyrus
Repository to
• |
check-in resources |
• |
maintain multiple environments (design,
test, production) |
• |
define version and variant control |
• |
create new classes and library templates |

The Papyrus Repository stores documents
and resources with versions and validation
(from/to). This ensures that all content
and letters are the most current and approved
versions. Other features are the user role
management, print job management and automatic
software and resource distribution. The quality and corporate identity can be
dramatically improved by ensuring that correspondents
work with the same document resources and
text elements which are approved and stored
in the common Repository. Built-in
templates ensure a consistent appearance to all correspondence reinforcing the corporate
and product branding.
Sharing the same document resources and
templates for batch and ad hoc correspondence,
reduces development time and cost and ensures
corporate identity.
|