...
Request Detail | Detail Style | Example |
By Requester: | ||
Date of change | Date in MM/DD/YYYY format | 11/101/2010 |
Description of the port change | Descriptive blurb | Allow all workstations of the Application Development group access to the Oracle database port |
Ingress/egress characteristic | Descriptive blurb | Incoming on port 1521 |
Source Specification | Descriptive blurb | wk1.ucdavis.edu, wk2.ucdavis.edu, wk3.ucdavis.edu |
Destination Specification | Descriptive blurb | dbhost.ucdavis.edu |
The term of the change (indefinite or otherwise) | One-liner | Indefinite |
Project(s) related to the requested rule(s) change | Descriptive blurb | Kuali Rice Implementation |
Urgent? | Pick either YES or NO | NO |
By Desktop Services: | ||
Modification in Effect? | Pick either YES or NO | NO |
By Firewall Policy Group: | ||
Reason for Disapproval | Descriptive Explanation | This request did not reflect urgency becasue of Reason A, Reason B, and Reason C. Please resubmit request. |
By Workflow Engine: | ||
Revert Firewall Modification | Checkbox | Autofilled by workflow if an URGENT request is disapproved. |
The request details in....detail:
- The details we are asking from the Requester are almost the same as those in the Simple Workflow tutorial. This time we decided to split Source Specification and Destination Specification into two fields and allow for the Requester to tell us that this is an URGENT request.
- The details of the request don't stop there. As the process moves along, we want the other responsible parties to add detail to the form.
- Once Desktop Services fields the request, we want to capture whether the firewall modification being requested is already in effect or not. Depending on the answer, the workflow will route the form to the appropriate party.
- If the Firewall Policy Group decides to disapprove the request, we want to capture their reason for doing so.
- If the request is URGENT, and the Firewall Gatekeeper already modified the firewall rules, and the Firewall Policy Group disapproved the request afterward, we want our workflow to automatically check a box that prompts the Firewall Gatekeeper to revert the modification.
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.
...