Papyrus WebPortal
More than just a pretty user interface.
The Papyrus WebPortal is a part of Repository’s functionality that offers Web-based applications to streamline your business. All information related to the web user, business data and document type and layout are stored in the WebRepository.
The Web browser functions are a multipurpose GUI that enables the customer or end user to view and interact with the business’ communication of virtually any type or format. Each end user’s experience is tailored to his or her role, enabling extensive flexibility either through the viewing of documents or interacting with them by filling in text and data. Document security, versioning and reconciling different taxonomies is taken care of by WebRepository.
Setting up a Papyrus WebPortal is easier than you think. The portal roles you create for one user can be applied to other users across the company, cutting down on implementation time and costs. Papyrus also delivers HTTPs server functions and integrates with third party HTTP servers. The full Papyrus Client text editing functions are available as a plug-in in the browser and all document formatting is performed centrally on the fly and are shown in PDF format in the browser.
Benefits/Gains to be achieved |
• |
A unified document interface and a single point of entry |
• |
Java coding not required |
• |
Seamlessly integrated Web-based e-document solution where data, documents and applications interact within the portal process definition |
• Document Framework Development
Graphical design of document resources. All resources, classes, versions, variants, jobs, etc. are stored in a central Repository. An integrated authorization system based on roles and policies eliminates unauthorized access and offers change management for document flow and sign-off. Features such as version and variant control, along with audit trailing, monitor changes in the document and keep track of letters produced by a variety of users.
• Business Application Data
The business application data can be directly read by Papyrus in any format, such as XML, ASCII and EBCDIC. Papyrus offers several standard data interfaces: Flat files, SQL queries, Adapters (i.e. MQ Series), HTTP, TypeManagers for DB/2 and Oracle. Data preparation or data tagging is not required.
• Process Management
The process management is used to request documents from the server, which then manages the completely independent document process. Upon completion, a status is returned.
• The Central Production Server
A central PC or UNIX server receives data from Web users via HTTP. It interfaces with data from the business application and collects document resources and layout definitions from the central Repository. The e-document is generated on the fly and sent to the user in PDF format for viewing and local printing.
• Central Server Printing, Pooling and Archiving
All Web-generated documents can be automatically archived, viewed, searched, and printed locally or centrally from virtually any platform and printer. Pages retain their original look and feel, complete with text, graphics, photos, and color and documents remain available for as long as they serve a useful purpose or legal requirement. These rules also govern the removal of documents when they have outlived their usefulness. |
