Page Comparison

...

After going through the easy and expedient process of requesting Work Groups, the Kuali Rice administrator has notified us that the following groups are available for use in our workflow:

Responsible Party	Work Group
Requester	Initiator.Role.RuleAttribute <-- i.e., this could be anybody
Desktop Services	ucd.IET.DES.DevelopmentSupport.WorkGroup
Firewall Policy Group	ucd.IET.AppDev.FirewallPolicyGroup.Workgroup
Firewall Gatekeeper	ucd.IET.DCCS.FirewallSysAdmin.Workgroup
Super User Workgroup	ucd.IET.AppDev.KualiRice.SysAdmin.Workgroup
Default Exception Workgroup	ucd.IET.AppDev.KualiRice.SysAdmin.Workgroup
Process Owner	ucd.IET.AppDev.FirewallPolicyGroup.Workgoup Note 1:

Info
Notice that the Kuali Rice Administrator identified ucd.IET.AppDev.KualiRice.SysAdmin.Workgroup even though that group is not involved in our business process. We'll need to identify a Super User Workgroup and Default Exception Workgroup when we create Document Types.

...

Notice that the Kuali Rice Administrator identified ucd.IET.AppDev.FirewallPolicyGroup.Workgoup as the Process Owner. We'll use Process Owner as part of a naming convention throughout the development of this workflow.

Looking at our workflow diagram, we build a table documenting who should act on which node and what action we're requesting of them:

Node	Responsible Party	Action Requested
Request	Initiator.Role.RuleAttribute (whoever creates the document)	SUBMIT
Review Current Configuration	ucd.IET.DES.DevelopmentSupport.WorkGroup	APPROVE
Review Request	ucd.IET.AppDev.FirewallPolicyGroup.Workgroup	APPROVE
Fulfill Request	ucd.IET.DCCS.FirewallSysAdmin.Workgroup	ACKNOWLEDGE APPROVE
Fulfill Urgent Request	ucd.IET.DCCS.FirewallSysAdmin.Workgroup	ACKNOWLEDGE APPROVE
Review Urgent Request	ucd.IET.AppDev.FirewallPolicyGroup.Workgroup	APPROVE
Acknowledge Configuration	Initiator.Role.RuleAttribute	ACKNOWLEDGE

...

Versions Compared

Old Version 92

New Version 93

Key