Page Comparison

...

In this tutorial we will use eDocLite to facilitate a business process called Request Firewall Change, but this time the process involves more responsible parties, more decisions to be made (not necessarily by people), more notifications, a few subprocesses, a way of skipping steps in the process, and a way to "un-fulfill" a request that was already fulfilled (yikes!!!).

Also, instead of expanding on the workflow in the Simple Workflow tutorial, we will build a brand new workflow. Whereas the previous tutorial has a "get-your-feet-wet" flavor, we will give this one the "little-fish-in-the-big-pond" treatment. This means we will act as though there are several departments (tens of or hundreds of) at UCD who are already using eDocLite for all kinds of workflows and therefore, we must use conventions (naming and styling conventions) that will prevent our work from colliding with other departments' work and do so without confusing us at the same time (a daunting task when similar responsibilities are distributed all over a large organization).
In this case, there may be several other departments who:

• administer their own firewalls
• have a Firewall Request Change process that's different from ours (ours, being that IT department somewhere out there)
• have their own desktop services group that has the same responsibility as our Desktop Services group
• have a group called Desktop Services, but does not field firewall change requests

Development Steps

1. Study the Business Process
2. Gather the Required Details
3. Create a Workflow Diagram
4. Create Users
5. Create Work Groups
6. Create the Parent Document Type
7. Create the Child Document Types
8. Create the eDocLite Form
   • Create the Definition
   • Create the Stylesheet
9. Create the Rule Template
10. Create Routing Rules
11. Ingest XML Files
12. Simulate the Business Process

...