Please refer to the Kuali Documentation directly for workflow information. Please note that we recommend using groups for routing rather than individual users. If an individual user is changed it will only impact future requests, so if a person has left the University, in progress workflows will be stuck. If you use a group, then members can come and go without causing an issue with records that are in progress. Groups are currently maintained by ITS. You can submit a request for a workflow group or changes to the group via the Technology Support Center Portal at techsupport.uconn.edu.
OR
Please refer to the Kuali Build documentation directly for workflow information:
Please note that we recommend using groups for routing rather than individual users to maintain workflow functionality, in the event there are changes to the individual’s credentials or employment status.
For example, if an individual defined in a particular workflow leaves the University, any records in progress will be stuck. Groups are recommended, as members can come and go without causing an issue with records that are in progress. Groups are currently maintained by ITS. You can submit a request for a workflow group or changes to the group via the Technology Support Center Portal at techsupport.uconn.edu.