Concept and Architecture

To deliver any type of business application, via fat client (desktop), browser-based or mobile application, we always need to bring the following elements together: Data, Process/Tasks, Content, Business Rules and User Interface.

Elements of Business Applications

Elements of Business Applications

The Papyrus Platform integrates data, activity, content, rules and GUI and manages all objects needed to work in collaboration on a business case from a central object metadata repository. Security and auditing, versioning, change management and deployment at date and time are standard functions of the system.

Security Concepts

Papyrus Objects uses an integrated authorization system, to ensure that no user or program can access the system without proper authorization.

Today, most companies have existing infrastructures with security and authorization products already in use. Obviously, it is not practical for an organization to manage user information in Papyrus Platform separately. So, Papyrus Platform provides standard interfaces, such as LDAP, to access such information.

Business Data integration

Papyrus offers a unique adapter approach to integrate with existing systems and databases.

Standard adapters are available for Web services (SOAP, REST/ATOM), MQ, SMTP, POP3, LDAP, SAP XOM, Java, XML, MS SharePoint, CMIS and many more.

Bi-directional connections to databases (Oracle, DB2, MS SQL, etc.) are supported with the Papyrus TypeManager.

Adaptive Process Management

Papyrus Business Process Management executes the process model and allows for straight-through processing (STP) as well as human workflow. The process model can be created by the end-user during execution of the business process. The user can choose from a wide a wide variety of (pre)-defined tasks and is able to define the business rules in natural language, as well.

There are two types of tasks (actions) that can be performed in a process:

  • User tasks (performed by end user)
  • Service tasks (performed by the system)

BPM Model

Papyrus Business Correspondence

Content - Outgoing and Incoming

Objects-based Papyrus supports all document types - including images, photos, PDFs, Microsoft Office - for delivery, upload, management and viewing through the platform’s strong capabilities for Document Capture and Document Creation.

Papyrus Correspondence

The purpose of Papyrus Correspondence is to simplify document template creation and document development for high-quality communications. Through modularization, it is possible to update and reuse existing, pre-approved elements documents instead of each user storing and re-creating their own set of (possibly unapproved) text blocks or graphics. It is also possible to grant user rights to modify a paragraph under certain conditions while the rest of the document remains protected.

Papyrus Capture

Papyrus Mobile integrates seamlessly with Papyrus Capture to allow automatic processing of captured documents (scan, e-mail, upload). Take a photo or upload from the library and Papyrus adds it to the Case.

Document classification, index extraction, process data extraction and automatic and manual verification and correction are part of the standard Papyrus Capture solution.

Mobile Capture

Rules in Natural Language

Rules in Natural Language

Natural Language (NL) is a query language that enables end users to define business rules:

  • Using everyday language instead of programming a query with complicated expressions
  • Without knowing the underlying data structure

NL can be specified by entering terms (automatically recognized) or using the drop-down list box that shows suggestions. During typing, the list adjusts to matching terms - the NL edit line is applying a sort of “filter” that reduces entries to only those matching what already has been typed.

User Interface

Many organizations are supporting multiple platform-specific versions of the same application because the project began when there was only a need to support a specific device or platform. But over time, the need to support multiple devices and platforms was added to the requirements.

The Papyrus Platform supports a cross-platform and cross-device architecture with Papyrus EYE/Widgets.

Platform-specific implementation

Cross-platform mobile devices - "Define once - Deploy to many"

An EYE on User Interface

Papyrus EYE/Widgets allow the creation of attractive and intuitive tailor-made GUI applications using drag-and-drop widgets, and offering style sheets for a corporate look and feel.

Your own in-house application market with Papyrus

With the Papyrus Platform, this means "Define Once - Deploy to Many” Define instead of Write - as with the Papyrus Platform there is no writing (platform-specific) code - and Deploy to Many because the Papyrus Platform comes with a platform- and device-specific Papyrus EYE/Widgets client that accesses applications from the Papyrus Repository (your own application market). There is no need to bring your business applications to the Apple Store or Android market.