...
Warning |
---|
Please note the following areas are still under development:
|
...
Content and Events Synchronisation
...
Expand | |||
---|---|---|---|
| |||
Learn Amp concepts
Defining Terms
|
...
Expand | |||
---|---|---|---|
| |||
title |
| ||
Expand | |||
|
Expand | ||
---|---|---|
| ||
Degreed is not an LMS. As such, its compliance reporting is not capable of supporting many use cases that Learn Amp does support. This section explains some implications of these differences. | ||
Note | ||
Due to limitations in Degreed, we
|
Tasks and Required Learning scenarios
|
Tasks and Required Learning scenarios
Note |
---|
Due to limitations in Degreed, we strongly recommend using Learn Amp as the source of truth for compliance reporting. |
...
Expand | ||
---|---|---|
| ||
There are multiple ways this scenario could occur:
|
...
FAQs
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
Data syncs are usually instant. Learn Amp syncs data to Degreed immediately after a create/update/delete event as a ‘background job.’ There is a small possibility that the sync could take slightly longer if the background job queue is busy. It is also possible that this could be delayed from the Degreed side, especially for Learn Amp’s batch actions. This is due to Degreed limiting the number of calls a single API client can make to 70 requests per minute (rpm). |
Expand | ||
---|---|---|
| ||
|
...