Four-Step Workflow
This form uses a four-step workflow, demonstrating a common pattern in form development.
- The original user submits the form
- The form goes to some dispatcher group, assigned when Managing Form Section Permissions, who then routes the form to the approver
- The assignee approves or rejects the form
- Before being fully processed the form, if approved, returns to the dispatcher (or some other group) to update an external business process
Two-Step Workflow to Group
This form demonstrates a way the above example can be simplified.
- The original user submits the form
- The form goes to a group containing all advisers who can potentially approve the form
The downside of this approach is that all advisers get email alerts for all forms and it relies on them proactively check the queue for their advisees
Two-Step Workflow with User Assignment
- The original user submits the form
- Based on the user's advisor selection the form is routed to that adviser alone.
The downside of this approach is it relies on the student knowing their adviser and the adviser being available to process the form, whereas routing through a dispatcher that person can confirm both of those things. It would also be possible for the original submitter to assign the form to a NetID outside of the list provided, though a step can be added to confirm a signature before completing the form.
Four-Step Workflow without CSS
This form is the same as the four-step workflow above but without any CSS or JavaScript.
Sample Fields using Bootstrap
This is not a functional form but shows some of the field styles available using the Bootstrap framework.