The User Role

The Papyrus Desktop features a simple user interface that requires no formal training and is very easy to use.
The Desktop application provides users access either to a number of libraries to select letters, or the letter can be created by a message event received through an ADAPTER and is kept in the work folder of the user.

Any User Can Generate Highly Customized Letters

Dynamic document assembly executes the correct text elements, graphics and other document resources defined and fills the letter with the variable customer information. The user can be prompted to customize authorized text and data fields. He has access to a simple text editor that offers typing text freely, using a spell checking utility, underline, cut, copy and paste, selecting a certain font, etc. Depending on their authorization and on the definition of the letter application, only some parts or all of the letter can be edited.

The Document Process

Papyrus Desktop with check box letter application:

The user can select or deselect letter elements and distribution options. The letter was defined by the administrator to be assembled from a number of elements of different types. By using the parameters in the template the administrator has defined which changes the user is allowed to make. Rules as to which elements are exclusive are checked. Data fields, used as letter variables, have range definitions so that the user cannot type in wrong data. Other rules verify that the letter can only be produced when certain conditions apply.

The customer service staff or any user can generate highly customized, high volume and ad hoc letters in a minimum amount of time.

Letter Preview and Edit

To actually create and preview the letter, the Papyrus Client is started as a Plug-In. The letter is previewed in perfect fidelity (WYSIWYG).

For editing text, the user opens the defined text prompts inside the letter. An easy to use text editor provides all commonly required
text features.

For editing variables inside the letter, the Papyrus Client supports a prompting feature, which was defined in Papyrus Designer and used as a building block.

The 4 EYE Principle:

The user only sees the option 'Sign Off' and makes the
document available for verification to a supervisor. The
supervisor can, according to this role and document state,
perform further editing or finally release the document.
The document state can be sent to the application that requested the document.

The User Management

Papyrus Objects uses an integrated authorization system,
to ensure that no user or program can access the system
without the proper authorization. Authorized users have
full management control of all phases of correspondence
production, from document assembly to content approval.

Defining a Corporate Organization Hierarchy

All departments and their employees with their various roles are to be known to the system. Once the organization is defined, the applications to be implemented with Papyrus Objects need to be defined. These are organized in libraries, which group all objects and documents related to one user role together.

The Role and its Defined Privileges

Each user receives at least one role which can also have a
privilege defined. The privilege string is defined in the method definition of the object. The Policy defines which instances a user is allowed to access.

Example:
The user may be allowed to perform the method ‘delete’ for one particular letter but he is only allowed to access the letter of a certain department or one specific application type.

Authorization and Security

User Roles and Policy define what the user sees on the Papyrus Desktop GUI having a certain role. Security is provided by data and communication encryption.

Interfacing with RACF, LDAP and ACTIVE D:
Logging onto the Papyrus Desktop executes the given ID
and password from the customer’s existing security system. Papyrus can interface with the company security system on the mainframe (i.e. RACF) and provides Adapter i.e. for LDAP. Papyrus Objects can also maintain security information by itself in its own storage.

The letter process uses state definition

A typical state sequence is:

The message handler always checks if an object is allowed to access the system.