 rotate(10)'/%3E%3Cpath d='M.038.113v.15l.15.088.15-.088v-.15L.188.025l-.15.088Z' stroke='%23c44900' stroke-width='.0375' transform='rotate(10)'/%3E%3C/svg%3E)
Track: Editor
About 50 minutes, after Foundations. The longest track, because Editors do the substantive work of the portal.
WHAT TO TAKE FROM THIS
- Duplicate before you build. Most new roadmaps are variants of one that already exists, and copying leaves you free to change only what differs.
- A roadmap always opens read-only. Switch Make Editable on before anything can change — this is a guard, not a fault.
- The action icons live at the right-hand end of each slot row. Scroll the table sideways to reach them.
- Save Draft is the normal way to stop. Cancel throws away everything since you opened the roadmap, and deleting a slot cannot be undone.
TRY IT IN THE PORTAL
- Open a roadmap with the pencil icon and switch Make Editable on.
- Scroll the slot table right until you can see the three dots, pencil and trash can.
- Switch Make Editable back off and confirm the row actions become unavailable.
- Find a published roadmap close to one your department needs and click the copy icon to see how duplication works.
CHECK YOURSELF
The Make Editable toggle. It is off by default every time you open a roadmap.
Save Draft. The roadmap stays unpublished and you can reopen it later and pick up where you left off.
You cannot. Rebuild it with Add Slot. There is no undo on a deletion.
Practice safely. If your institution has a sandbox or training catalog year, build there. Otherwise work on a draft you created yourself, use Save Draft, and do not click Submit for Review during training.
WHAT TO TAKE FROM THIS
- The wizard is linear except for one decision. Step 2 asks what kind of requirement this is, and your answer rewrites step 3 completely.
- Changing the type later resets every step after it. Decide before you click Next.
- Whatever type you pick, steps 4 to 7 — Locations, Prerequisites, Notes, Review — are identical.
- A note typed at step 6 is not saved until you click Add note to table.
- Only courses from the roadmap's own catalog year are offered, and prerequisites on the course you pick are detected for you.
TRY IN THE PORTAL
- On a draft roadmap, click Add Slot, then the pencil on the new row.
- Complete step 1, then at step 2 choose Core curriculum category. Pick a category code, set min and max, and watch the approved course list fill itself.
- Go back to step 2 and switch to One specific course. Notice that step 3 has changed completely and your earlier selections are gone.
- Finish the wizard through Locations, Prerequisites, Notes and Review, then Save Draft.
One specific course. Prerequisites on HIST 3300 are detected automatically.
Course list or range. Choose ‘Add a range of courses’, then answer Yes to the multi-level question and set a lower and an upper limit.
Nothing. The entry is standardised — the portal adds the 1300–4300 range and the degree-plan note itself.
Everything after step 2 resets. You will redo steps 3 to 7.
WHAT TO TAKE FROM THIS
- Submitting emails you and the portal Manager. The Manager assigns both reviewers and starts the review.
- Two approvals are always required, in order: Department Chair, then Student Success Director.
- Publication is automatic. Nobody presses a publish button.
- If a reviewer requests changes, the roadmap comes back to you with their comment and the cycle restarts at Submit — not at the beginning.
TRY IT IN THE PORTAL
- Open Roadmap Workspace › My Submissions and look at the status of anything you have submitted.
- Open a submission and find the approval timeline at the foot of the page.
- Read one reviewer comment, if there is one, and note that it is visible to everyone who touches the roadmap afterwards.
CHECK YOURSELF
Nobody. It publishes automatically the moment the Student Success Director approves.
Back to you with their comment. Fix it and submit again; the cycle restarts at Submit.
Two, always: the Department Chair of the program, then the Student Success Director.
WHAT TO TAKE FROM THIS
- The University Catalog is revised every year, so roadmaps are revised and re-approved every year.
- Catalog Year Rollover copies a whole catalog year forward in one action, across all eight underlying tables, with new record IDs.
- Rollover produces drafts only. Nothing is published by it.
- Every rolled-over draft still has to be opened, revised against the new catalog and submitted for review in the normal way.
TRY IT IN THE PORTAL
- Open Catalog Year Rollover and read the panel listing what gets copied. Do not submit unless you have been asked to run a real rollover.
- Open All Submissions and identify any drafts created by a previous rollover.
- Pick one and work out what would need to change for the new catalog year.
CHECK YOURSELF
No. It creates drafts. Each one still needs revising and approving.
The rebuilding, not the thinking. Every draft still has to be checked against the new catalog.
The one after your source year. The portal sets it automatically.
You are ready when you can do all of this without looking it up
Next: if you are also a Manager, continue to Track: Manager. Otherwise, keep Adding a Course Requirement and The Five Requirement Types bookmarked.