Professional Development

[CB DRAFT] PRDV432: No-Code AI Automation

0% complete
0% complete
Resume

  • Unit 5

    ‹Unit 4 Assessme...
    5.1: What Are A...›

    Unit 5:
    Introduction
    This unit introduces AI agents and shows you how they differ from simpler automation tools. Agents can take a more active role in a workflow, which makes them useful when a task needs some level of decision-making or adjustment.
    You then begin to connect agents with no-code workflows. This is an important step because it helps you see how different kinds of automation can work together. As you move forward, you will be better prepared to think about where an agent can help and where a simpler workflow is the better choice.
    Unit 5: AI Agents
    Introduction
    As you move into this unit, you shift from using automation that follows fixed steps to working with systems that can make more independent choices. This is a major step in your no-code journey, because it opens the door to automation that can respond to changing situations, not just repeat the same task. If you understand how agents work, you can begin to design workflows that feel more flexible and useful in real work.
    You will build on the earlier units on rule-based automation, AI-enhanced workflows, and prompt writing. Now the focus is on what AI agents are, how they act, and how they can fit into no-code systems. This matters because many tasks in work and daily life need both structure and judgment. This unit helps you think about when an agent can help, and when a simple workflow is the better choice.

    This unit aligns with the following Course Learning Outcomes:

    • Differentiate traditional workflows from AI agents.
    • Build simple AI agents with free tools and prompting techniques.
    • Design agent behaviors that support decision-making and multi-step task execution.
    • Combine AI agents with no-code workflows to handle complex scenarios.

  • Introduction

  • Course Introduction

  • Unit 1

  • 1.1: Understanding No-Code Automation

  • 1.2: Types of Automations: Rule-Based, AI-Enhanced, and Agents

  • 1.3: Exploring Free No-Code Tools

  • 1.4: How Generative AI Powers Automation

  • Unit 1 Conclusion

  • Unit 1 Assessment

  • Unit 2

  • 2.1: Spotting Repetitive Tasks in Your Work

  • 2.2: Creating Visual Process Maps

  • 2.3: Defining Triggers, Actions, and Conditions

  • 2.4: Prioritizing Automation Ideas

  • Unit 2 Conclusion

  • Unit 2 Assessment

  • Unit 3

  • 3.1: Getting Started with No-Code Platforms

  • 3.2: Connecting Applications and Moving Data

  • 3.3: Adding Conditional Logic

  • 3.4: Troubleshooting Common Workflow Issues

  • Unit 3 Conclusion

  • Unit 3 Assessment

  • Unit 4

  • 4.1: Integrating Free Generative AI Services

  • 4.2: Using AI for Dynamic Content Tasks

  • 4.3: Creating Responsive AI-Enhanced Workflows

  • 4.4: Writing Effective Prompts for Automation

  • Unit 4 Conclusion

  • Unit 4 Assessment

  • 5.1: What Are AI Agents?

  • 5.2: Building Your First Simple AI Agent

  • 5.3: Adding Decision-Making to Agents

  • 5.4: Combining Agents with No-Code Workflows

  • Unit 5 Conclusion

  • Unit 5 Assessment

  • Unit 6

  • 6.1: Testing and Debugging Automations

  • 6.2: Ethical and Privacy Considerations

  • 6.3: Adding Human Oversight and Error Handling

  • 6.4: Planning for Long-Term Use and Scaling

  • Unit 6 Conclusion

  • Unit 6 Assessment

  • Study Guide

  • Final Exam

‹Unit 4 Assessme...
5.1: What Are A...›
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 372 of /course/view.php: call to core\output\core_renderer->footer()