What is a Workflow?
In Axis LMS, a "Workflow" is series of "Events" that get fired off sequentially after something "Triggers" its initiation.
A Workflow can be comprised of one or more "Actions". An action might be an enrollment (or disenrollment) into an Online Course, adding (or removing) a User to a Usergroup, or Awarding (or revoking) a Certification from a Certification Program, among many others.
A Trigger is usually an event initiated by an entity; this entity may be the admin, a manager, a user, or even an import. An example of an admin event might be a User being Added to the System; an example of a User event might be becoming Certified in a Certification Program, or redeeming a Keycode.
Another way of thinking of this combination is customizing existing functions of the system to do something more. As an example, Adding a User to the LMS will create a new User Account. Both halves of this ("Adding a User" and "creating a new User Account") are a native Workflow and Trigger. By creating your own Workflow or Trigger, you can latch onto these existing functions, and customize them to do more; such as sending an email to the admin when a User is Added.
Conditions can also be introduced to the ecosystem, so that a Workflow may only trigger under specific conditions, or that only parts of a Workflow will trigger if several Conditions are applied to it.
In Axis LMS, a "Workflow" is series of "Events" that get fired off sequentially after something "Triggers" its initiation.
A Workflow can be comprised of one or more "Actions". An action might be an enrollment (or disenrollment) into an Online Course, adding (or removing) a User to a Usergroup, or Awarding (or revoking) a Certification from a Certification Program, among many others.
A Trigger is usually an event initiated by an entity; this entity may be the admin, a manager, a user, or even an import. An example of an admin event might be a User being Added to the System; an example of a User event might be becoming Certified in a Certification Program, or redeeming a Keycode.
Another way of thinking of this combination is customizing existing functions of the system to do something more. As an example, Adding a User to the LMS will create a new User Account. Both halves of this ("Adding a User" and "creating a new User Account") are a native Workflow and Trigger. By creating your own Workflow or Trigger, you can latch onto these existing functions, and customize them to do more; such as sending an email to the admin when a User is Added.
Conditions can also be introduced to the ecosystem, so that a Workflow may only trigger under specific conditions, or that only parts of a Workflow will trigger if several Conditions are applied to it.