Blocks: Course Request Manager
Description
A real time saver for site admins who needs to process requests for new course setups. The course request manager block allows the admin to easily design and deploy custom course request forms which can be used by users with appropriate permissions.
Unlike the moodle core request feature which uses a single text box for information on the request, course request manager allows the administrator to design course request forms with up to 15 form fields for gathering request data from a user. Form elements may include text areas, text fields, drop down lists, check boxes etc. Forms can be created and managed using a simple and easy to use form editor.
The block is ideally suited for administrators who want to deploy an internal moodle request system and avoid requests sent via email or other communication methods. It aims to improve on the core request feature by adding the ability to custom design request forms.
Features
The block also contains a suite of features for managing, approving and commenting on requests.
- Design custom request forms
- Manage course requests
- Bulk approval of course requests (new in version 3)
- Automatically send confirmation emails
- Attach comments to requests
- Bulk request operations (new in version 3)
- View request history etc
- Design custom notification emails
- Set fields to mandatory or optional (new in version 3)
The block is designed to improve workflow in managing and approving course requests.
It has been developed by Daniel McSweeney and Kyle Goslin from the Institute of Technology Blanchardstown, Dublin
== Screencasts (Version 3) ==
A series of short screencasts on the setup and use of course request manager version 3.x for moodle
Setting the admin settings
A quick overview of the various administrator settings for course request manager.
eMail Configuration
Setting the eMail configuration options for the course request manager block for moodle 2.
Setting up the request form - page 1
Setting the configuration options for the first page of the course request form.
Setting up the request form - page 2
Setting the configuration options for the second page of the course request form.
Making Requests - User Perspective
An overview of the request process from an end user perspective.
Managing Requests - Admin Perspective
An overview of the request management process from an administrator perspective.
Useful links
Screenshots
Cannot downgrade block_cmanager from 2013041131 to 2013041131.
Debug info:
Error code: cannotdowngrade
Stack trace: ◦line 258 of /lib/upgradelib.php: downgrade_exception thrown
◦line 30 of /blocks/cmanager/db/upgrade.php: call to upgrade_block_savepoint()
◦line 813 of /lib/upgradelib.php: call to xmldb_block_cmanager_upgrade()
◦line 362 of /lib/upgradelib.php: call to upgrade_plugins_blocks()
◦line 1544 of /lib/upgradelib.php: call to upgrade_plugins()
◦line 349 of /admin/index.php: call to upgrade_noncore()
Site Administration -> Plugins -> Enrolments -> Self enrolment -> Add instance to new courses
Then there is a bug in that the user provided enrollment key is not shown on the course edit page. The reason is that when the new course is created it adds a self-enrollmnet method automatically with a random key. When CRM adds it's self-enrollment method with the key provided by the user, it is not first in the default sort order so it is effectively hidden. I worked around this by adding this hack code to lib/course_lib.php before you call $DB->insert_record('enrol', $enrollmentRecord);
// disable all other existing self enrol methods, including any auto generated when
// new course created due to the "Add instance to new courses" setting being enabled for self enrollments.
// This way the new record added below will be the active one.
$rs = $DB->get_recordset('enrol', array('enrol' => 'self', 'courseid' => $nid));
foreach ($rs as $self_enrol) {
$DB->update_record('enrol', array('id' => $self_enrol->id, 'status' => 1));
}
$rs->close();
It would be nice if CRM could handle this situation. Let me know if you have any questions about the issue or if you prefer a bud filed.
Josh
In Moodle 2.5 a new field had been added called "customint6", this cause some issues with CRM, as before this it did not exist!
A new version of CRM is available now resolving the self enrollment issues!
Thank you,
Kyle.
Josh