2.2 Creating Visual Process Maps
SOURCE: 2.2 Creating Visual Process Maps
2c. Define triggers, actions, conditions, and data requirements for an automation.
2c.1. Unit 2.3 explains that a good automation needs a clear trigger, a set of actions, any conditions, and the data it must use. These parts help you define what starts the workflow and how it should respond. DISCUSS: If you were designing a simple automation, how would you decide what should trigger it, what it should do, and what data it needs to work correctly?
To review, see:

Last modified: Thursday, 18 June 2026, 1:28 PM
Callback before_footer in local_aigrade component should be migrated to new hook callback for core\hook\output\before_footer_html_generation
  • line 7225 of /lib/moodlelib.php: call to debugging()
  • line 7292 of /lib/moodlelib.php: call to {closure}()
  • line 71 of /lib/classes/hook/output/before_footer_html_generation.php: call to get_plugins_with_function()
  • line 987 of /lib/classes/output/core_renderer.php: call to core\hook\output\before_footer_html_generation->process_legacy_callbacks()
  • line 94 of /mod/page/view.php: call to core\output\core_renderer->footer()