{"id":97,"date":"2024-09-20T14:41:11","date_gmt":"2024-09-20T18:41:11","guid":{"rendered":"https:\/\/carleton.ca\/curriculum\/?page_id=97"},"modified":"2026-02-09T13:16:39","modified_gmt":"2026-02-09T18:16:39","slug":"section-d-workflow","status":"publish","type":"page","link":"https:\/\/carleton.ca\/curriculum\/section-d-workflow\/","title":{"rendered":"Section D: Workflow"},"content":{"rendered":"\n
\n
\n\n \n \n \n \n
\n\n \n
\n
\n\n

\n Section D: Workflow\n <\/h1>\n \n <\/header>\n <\/div>\n\n <\/div>\n\n \n\n <\/div>\n<\/section>\n\n\n\n\n
\n

\n Table of Contents\n <\/h2>\n
\n
\n \n
\n
\n \n 1.\n <\/span>\n\n \n 1.0 Overview\n <\/a>\n <\/div>\n\n <\/div>\n \n
\n
\n \n 2.\n <\/span>\n\n \n 2.0 Receiving workflow notification and logging into the CMS\n <\/a>\n <\/div>\n\n <\/div>\n \n
\n
\n \n 3.\n <\/span>\n\n \n 3.0 Reviewing a proposal\n <\/a>\n <\/div>\n\n <\/div>\n \n
\n
\n \n 4.\n <\/span>\n\n \n 4.0 Editing a proposal\n <\/a>\n <\/div>\n\n <\/div>\n \n
\n
\n \n 5.\n <\/span>\n\n \n 5.0 Rolling back a proposal\n <\/a>\n <\/div>\n\n <\/div>\n \n
\n
\n \n 6.\n <\/span>\n\n \n 6.0 Approving a proposal\n <\/a>\n <\/div>\n\n <\/div>\n \n
\n
\n \n 7.\n <\/span>\n\n \n 7.0 How to Rollback when Workflow Change is Required\n <\/a>\n <\/div>\n\n <\/div>\n <\/div>\n\n <\/div>\n<\/div>\n\n\n\n

1.0 Overview<\/h2>\n\n\n\n

When a submitter \u2018confirms and submits\u2019 a proposal for a course or program, workflow<\/strong> is initiated. The workflow is routed either through the minor or major modification steps as approved by Senate. Also built into the workflow are notification steps where individuals or groups will be notified of changes but no approval action is required.<\/p>\n\n\n\n

2.0 Receiving workflow notification and logging into the CMS<\/h2>\n\n\n\n

There are two types of notifications automatically generated by the system:<\/p>\n\n\n\n

1) Approver \u2013 requires action within workflow<\/p>\n\n\n\n

2) FYI \u2013 does not require action in workflow but this type of notification provides information that may require action outside of workflow. This includes committees, non-academic units and units who are included in the course ecosystem.<\/p>\n\n\n\n

Step 1: When a submitter submits a proposal, workflow is initiated. Immediately, the chair or director of the academic unit receives notification from CLWK (CourseLeaf Workflow) in an email automatically generated through the system. You will receive an email for each item that requires your approval. The following is an example of an email routed to the approver:<\/p>\n\n\n\n

\"Screenshot<\/figure>\n\n\n\n

Step 2: Click the link in the email to direct you to log into Carleton Central. Note that faculty members will automatically have access to view and submit proposals via the Faculty Services tab. Administrative staff with approval will have access via the Employee Services tab. Under each respective tab click Curriculum Management System and click Continue to bring up the Pages Pending Approval screen.<\/p>\n\n\n\n

3.0 Reviewing a proposal<\/h2>\n\n\n\n

Step 1: On the Pages Pending Approval screen, select the role appropriate to your approval authority. Note: although you may select different roles in the drop-down menu, you will only be able Edit, Rollback, or Approve a course or program associated with your role.<\/p>\n\n\n\n

\"Screenshot<\/figure>\n\n\n\n

Step 2: Click on the item to be reviewed in the Page panel. The proposal will display below.<\/p>\n\n\n\n

\"Screenshot<\/figure>\n\n\n\n

Useful features on this page:<\/p>\n\n\n\n