...
The typical lightweight workflow involves someone submitting a request for something, someone with authority reviewing that request and then approving or disapproving it, and then someone else to fulfill the request. In this tutorial we will use eDocLite to facilitate a business process called FirewallChangeRequest. An IT department somewhere out there implemented this process for use by programmers who work in other departments. When a programmer needs access to any services protected by the IT firewall, s/he submits a request via e-mail to the Firewall Policy Group mailing list. Any one member in the Firewall Policy Group can review the request and approve or disapprove it.
The Request Details
As part of the process, the Firewall Policy Group requires that anyone who wants the firewall rules modified must provide the following details:
...
Request Detail
...
Example
...
Date and time for change
...
January 1, 2010
...
Description of the port change
...
Allow all workstations of the Application Development group access to the Oracle database port
...
Ingress/egress characteristic
...
Incoming on port 1521
...
Destination/source specification
...
Source: wk1.ucdavis.edu, wk2.ucdavis.edu, wk3.ucdavis.edu Destination: dbhost.ucdavis.edu
...
The term of the change (indefinite or otherwise)
...
Indefinite
...
Project related to the requested rule(s) change
...
Development Steps
- Study the Business Process
- Gather the Required Details
- Create Users
- Create Work Groups
- Create the Parent Document Type
- Create the Child Document Types
- Create the eDocLite Form
- Create the Definition
- Create the Stylesheet
- Create the Rule Template
- Create Routing Rules
- Ingest XML Files
- Simulate the Business Process
The Business Process
Here's a diagram of our business process:
In using eDocLite to facilitate this process, we'll need a few things:
- A form to capture the request details.
- A way to bring the request to the attention of the Firewall Policy Group.
- A way for any member of the Firewall Policy Group to either approve or disapprove the request.
- A way for the requester to get the details on the actions taken on the request.
Development Steps
...
- Create the Definition
- Create the Stylesheet
...
The Request Details
As part of the process, the Firewall Policy Group requires that anyone who wants the firewall rules modified must provide the following details:
Request Detail | Example |
Date and time for change | January 1, 2010 |
Description of the port change | Allow all workstations of the Application Development group access to the Oracle database port |
Ingress/egress characteristic | Incoming on port 1521 |
Destination/source specification | Source: wk1.ucdavis.edu, wk2.ucdavis.edu, wk3.ucdavis.edu Destination: dbhost.ucdavis.edu |
The term of the change (indefinite or otherwise) | Indefinite |
Project related to the requested rule(s) change | Kuali Rice Implementation |
Create Users
Let's create an XML file that defines some users who will help us simulate the Request Firewall Change process. We have requester1 who will submit all requests and FPG1 & FPG2, who will be tasked with reviewing and approving (or disapproving) those requests.
...