Introduction
The population of auto-populated groups works off of platform events. This process constantly analyzes the platform events in order to understand if there are users needing to be added or removed to/from groups, based on these events.
Some events are processed asynchronously, meaning, with some delay. Depending on the events load at a given moment, the time needed to update the groups’ population may be delayed up to one hour.
Other events are processed synchronously, meaning, without delay.
This article elaborates which events are handled synchronously or asynchronously by the platform, dividing them into areas.
User-Related Events
This table lists the events related to user creation (by Superadmins) or self-registration.
|
Event |
Type of Process |
Notes |
|
User creation via self-registration |
Synchronous |
When a user self-registers or a Superadmin approves a user's registration, the groups’ population is handled synchronously. More details on user registration options. |
|
User creation by a Superadmin (from the User Management area) |
Synchronous / Asynchronous |
When a Superadmin creates a single user from the Users Management area, the group is populated with a synchronous process. When multiple users are created at one time (still from the Users Management area) the groups’ population is handled asynchronously. |
|
User creation or update via Single Sign-On |
Synchronous / Asynchronous |
Currently, some types of SSO are handled synchronously, and some are handled asynchronously. See below for details:
|
|
User is updated by a Superadmin (from the User Management area) |
Synchronous / Asynchronous |
When a Superadmin updates a single user from the Users Management area, the group is populated with a synchronous process. When multiple users are updated at one time (still from the Users Management area) the groups’ population is handled asynchronously. |
Enrollments-Related Events
This section lists the events related to course enrollments.
|
Event |
Type of Process |
|
User enrolled to course |
Asynchronous |
|
Updates to the user enrollment in a course |
Asynchronous |
|
User completed a course |
Asynchronous |
|
User unenrolls or is unenrolled from a course |
Asynchronous |
Branches-Related Events
This section lists the events related to users' assignments to branches.
|
User added to a branch |
Asynchronous |
|
User removed from a branch |
Asynchronous |
Asynchronous Events and Background Jobs
When more than 100 events are being created at the same time, the platform leverages background jobs to analyze the events. Events will be divided into multiple background jobs of 25 events each.
An example, when a Superadmin updates 125 users via CSV, 5 background jobs are created by the platform, with 25 events per background job.