Security example
This example describes a business process, analyzes the work performed
by various users, and describes how to create groups, document classes,
and folders to achieve appropriate security.
Imagine a credit card approval process where:
- A clerk adds new credit card applications to the object store.
For each application, the clerk selects the document class CCAppls and
files the new document in the /NewAppls folder. (The administrator has
configured a subscription to launch a workflow for each new document
in the CCAppls document class.) The workflow routes the application,
as an attachment, to an applications processor.
- An applications processor reviews the application and approves
it, denies it, or refers it to the analyst for further review. The decision
is noted in the document properties. Depending on the decision, the
workflow (using the processor's access rights) refiles the application
in the appropriate /Approved, /Denied, or /Pending folder.
- The analyst investigates all applications filed in the /Pending
folder. The analyst updates the application information as needed, approves
or denies the application, and returns it to the approval representative.
- The manager writes and updates procedures from time to time
and publishes them to the /Procedures folder. The manager spot-checks
processed applications and keeps an eye on the work in the /NewAppls
and /Pending folders.
- Everyone must be familiar with department procedures.
- The system administrator maintains workflows, publish templates,
and document classes.