Pulse Pro 2.0 introduces a powerful automation engine. Automation templates can be managed globally by users with appropriate capabilities. Based on these templates, automation instances are built upon automation templates, kept in sync with the automation template, with the option to override specific settings per instance. Automation conditions trigger the automation and rely on events and/or completion. Built in a modular way. Initially, there are conditions for activity completion, course completion, enrolments, session booking (mod_facetoface) and cohort membership. Automation actions are outcome of the automation, i.e. what’s actually happening. Built in a modular way. In the initial scope, this will be notifications. The first action we’ve built is a very flexible and powerful notification action.
Check it out on bdecent.io or read through the extensive documentation.
Good to know: All features of Pulse Pro 1.3 are still available in Pulse Pro 2.0, but should be considered legacy features. They are safe to use, and we will continue to maintain them, but we strongly recommend to implement notifications using the new automation engine. If you want to use Pulse Pro on Moodle Workplace or Totara, please contact us.
Pulse is a Moodle activity and can be added to courses like any other activity (e.g. page or quiz). Teachers can use Pulse for (1) notifications and (2) completion workflows.