Submit a ticket My Tickets
Login  Sign up

8. After-the-Fact Change Requests

8.1 Overview

After the time for building your schedule is over, you may want to make changes. Coursedog has a robust request feature that allows you to submit after the fact change requests. These requests will then enter a workflow for approval and, if approved, the change will be made in the system.

To access the requests page, select ‘requests’ on the left navigation menu. Here you can see requests that require your vote and that were created by you. 

8.2 Create a Request

To create a request, click ‘Create Request’ and select the type of request you wish to make. Rule Exception (we saw these is module 7) allows you to request permission to bypass a rule (e.g.: a standard meeting pattern rule). 'Section Change' allows you to make a proposal to add (including add from Course Inventory), edit or remove a section.


Taking 'Section Change' as an example, the next step is to specify which course and section you are making a request for.

Once you select a section, the corresponding form will appear and you will be asked to add a reason for making the request. 

The form will look exactly like a standard Section Form, so you can simply input whatever changes you want to make and they will appear at the top of the dashboard.

When you are ready to submit, you can press ‘Submit Request’ and the request will be sent to the associated approval workflow. 

8.3 Tracking a Request

To keep track of a request you submitted or want to follow, navigate to the request in the requests table and click the one you want more information about. 

You will be taken to the specific request dashboard where you can see the specifics of the request on the left as well as the approval progress of the request on the right. 

To see more information about the approval workflow of a request, select ‘Workflow’ in the request toolbox on the right.

Here you can see each step of the approval process. To get more information about a specific step, you can click the title of the step (for example, ‘Registrar Review’).

Section Change requests can be edited after they are submitted by users with the correct permissions.

Depending on the permissions set by your institution, upon editing the event and hitting ‘Save’ the workflow might reset or not. You will be notified of the appropriate downstream effects.

Within the request permissions for all products, the following two permissions are available. These permissions are used to control what options a user has when the edit a request.

If both permissions are set to "off", and a user edits a request, they will see the following message when they save. The message explains that saving the request will reset the workflow and disregard all existing approvals.

If one or both permissions are set to "on", a user will have a dropdown allowing them to choose a request reset option, as shown below.

Resetting the workflow means regenerating the workflow based on the workflow template defined in settings. All logic jumps and dynamic steps will be re-evaluated, and any new steps that result will be injected into the reset workflow.

There are the following options for resetting a workflow:

  1. Reset Workflow - All prior approvals will be disregarded. This is the default logic that will be implemented when a user does not have any of the extra permissions. This will reset the workflow, remove all existing approvals, and send the request back to the author step
  2. Reset Workflow - All Prior approvals will be maintained. This action will reset the workflow, but keep all existing approvals. If after the workflow resets, no new steps have been added, the workflow should remain at its current step. If any new steps were added to the workflow during the reset process, the workflow will be sent back to the first step that has not been approved.
  3. Do Not Reset Workflow. This action will allow users to save the request without resetting the workflow

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.