Automation engine feature
These actions embody the results of the automation process, defining the actual events that occur. They are constructed in a modular fashion, with the initial priority centered primarily on notifications.
Full list of features
Basic | Pro | |
|---|---|---|
| Notifications and reminders Automate course communication. | ||
| Custom notifications Keep students updated with custom notifications. | ✔ | ✔ |
| Placeholders Create personalized & dynamic communication. | ✔ | ✔ |
| Dynamic content Integrate book chapters and information about course activities (such as title, description, due date). | ✔ | |
| Header and footer Add text, images, logos or other branding elements to notifications. | ✔ | |
| Define recipients by role CC and BCC teachers (course context role) or parents (user context role). | ✔ | |
| Reminders Schedule notifications at fixed or relative dates – once or recurring. | ✔ | |
| Deep learning path integration Create dynamic and personalized learning pathways. | ||
| The Pulse course activity Use anywhere within the course content to trigger actions at specific points. | ✔ | ✔ |
| Availability-based triggers Uses availability conditions as triggers for actions, enabling dynamic and personalized learning pathways. | ✔ | ✔ |
| Completion and approval workflows New, flexible ways to mark activities as complete and to request approvals. | ||
| Complete when available Allows an activity to be marked as complete the moment it becomes accessible to the user. | ✔ | ✔ |
| Non-reversible manual completion Once the student has marked the activity as complete, the student cannot revoke it any more. | ✔ | ✔ |
| Completion after approval Teachers/parents/managers can give their approval in a very simple and intuitive way. | ✔ | ✔ |
| Reactions Enable recipients of notifications to react directly from the email without being logged into the platform or integrate reaction modules directly in your course activity. | ||
| Mark as complete Students can simply mark as complete the activity. | ✔ | |
| Rating Students can give a thumbs up or down to rate at any place within the content. | ✔ | |
| Approval Allows users with a selected role to approve a student's completion of a Pulse activity. | ✔ | |
| Confirmation for activity completion Integrate consent statements or other texts that have to be confirmed, approved or at least acknowledged by the student. | ||
| Confirmation types Choose your button: Acknowledge, confirm, choose or approve. | ✔ | ✔ |
| Add confirmation modal The user must confirm or cancel a modal with a custom text. | ✔ | ✔ |
| Credits Motivate students with rewards for completing modules or meeting criteria, supporting gamification, grading, and assessment. | ||
| Awarding credits The credits are updated in the user's profile field when the ad hoc task is running. | ✔ | |
| Define a credit score Assign credits to your students giving them rewards for completing modules or meeting certain criteria. | ✔ | |
| Styling and visualisation Customize the look and feel of your content within a Pulse activity. | ||
| CSS integration Integrate custom styling via CSS. | ✔ | ✔ |
| Display mode Define a boxed or normal style. | ✔ | ✔ |
| Box type and icon Choose from a variety of pre-designed box types and icons. | ✔ | ✔ |
| Presets Pre-configure settings that can be customized when used. | ||
| Managing presets by admins Creating, customizing and organizing presets for teachers. | ✔ | |
| Using presets by teachers Easy set up of Pulse activities. | ✔ | |
| Automation engine Scalable cross-course automation with monitoring and reporting. | ||
| Automation templates Ensuring consistency and scalability across courses while providing flexibility through automation instances. | ✔ | |
| Automation instances Initially adopting the template’s default settings, but instances can be modified. | ✔ | |
| Instance management Centralized system for managing automation instances, ensuring transparency and control. | ✔ | |
| Automation conditions Serving as triggers for automation and depending on events or task completions. | ✔ | |
| Automation actions So far there are only notifications, but there is more to come. | ✔ | |
| Suppress notification criteria Smart reengagement through suppression logic – notifications only when needed. | ||
| Suppression by module Preventing notifications from being sent once specific activities have been successfully completed. | ✔ | |
| Suppression by course completion Notifications are automatically prevented from being sent once a user has completed a course. | ✔ | |
| Monitoring and reporting Monitor engagement, track automation effectiveness, and identify areas for improvement. | ||
| User interaction Reports on user interactions, including reactions, invitations, reminders, self-marked completions, and approval status. | ✔ | |
| Automation schedule & notification queue Providing a detailed overview of all scheduled and sent notifications. | ✔ |