Home > Information > Focus Reports > Correspondence > Document Framework/The Developer Role

View pdf: English German Italian

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.


For document design and data definition the developer utilizes the graphical Papyrus Designer.
Papyrus Designer displays for the design process the DATA interface, the LOGIC, the LAYOUT and the PRINTER RESOURCES such as fonts, forms and logos, each on its fully formatted page. The development is greatly simplified by the integrated graphical user interface that supports cross referencing between data, logic and layout.

The functionality of the Papyrus Desktop:
The Papyrus Desktop has no hardcoded functionality for any special application. The user can communicate with all the objects which he has a direct or indirect relationship. Thus, it is guaranteed that the user can only access objects for which he is authorized.

From the idea to production of the business document in just days ensures shortest time to market cycle.

Business Analyst Role/Administrator

The administrator uses the Papyrus Desktop to access the Papyrus Library, assembling templates and adding criteria to the interface definitions. Version and Variant control enables the administrator to manage the lifecycle of the documents.

The adminisrtator uses the available definitions to create templates, customize them and store them to the Library. The template and library access is controlled by the authorization system.

He/she assembles the objects of a framework to new business documents without using the Papyrus Designer. He/she works with the Papyrus Desktop by pulling elements from the library, assembling and changing the parameters to define a new letter. Using templates, one can have thousands of special variations built from one Class definition.

He/she stores these letter elements to a library and assembles them to a set of letters. These letters can then be assigned to library folders. Obviously, reuse of letter elements is very simply supported by multiple references.

He/she customizes and defines how objects are presented on the Desktop and worked with by the users. This avoids extensive dialog programming like with Java.

He/she also assigns user authority and the access of the new business document in the library/application/menu hierarchy.

 

© 2008 ISIS Marketing GmbH - legal disclaimerImpressum • ISIS is not associated with Research Software Design (RSD), nor it's Papyrus Bibliography software.