Versions Compared

Old Version 5

changes.mady.by.user Emma Booth

Saved on

compared with

New Version Current

changes.mady.by.user Mollie Aspley

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning

Please note the following areas are still under development:

  • Updating visibility of content

  • Archiving/unarchiving content

  • Syncing Events and Event Sessions

  • Syncing other content types, like quizzes and surveys

  • SSO access via Degreed

...

Content and Events Synchronisation 

...

Expand
titleMapping/syncing of Tasks and Completion

Info

  • A Learn Amp Task creates a Required Learning in Degreed

  • The deadline set for the Task will be mapped to the Required Learning in Degreed.

  • The user/s and content outlined in the Task must also exist in Degreed for the Task to create a Required Learning.

    • Email is used to match users across Learn Amp and Degreed

  • Completing tasked content on Learn Amp will complete the Learn Amp task and verify the required learning in Degreed

  • If untasked content is completed on Learn Amp it will also be verified in Degreed, for that user.

  • Updating ‘complete by’/deadline in Learn Amp updates the ‘Due by’ date in Degreed 

    • Previous Overdue information is not kept in Learn Amp, so this is also not specifically kept in Degreed 

  • Events cannot be tasked in Learn Amp and therefore cannot be set as required learning in Degreed.

  • Events are marked as verified in Degreed when the Learn Amp Event is marked as complete. Please note that completion of an event in Learn Amp depends on the settings chosen for the event.

Expand
titleIMPORTANT: Degreed Limitations and Watchouts

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 strongly

  • When ‘verification’ is removed via the API, Degreed shows the content as ‘Completed’ 

  • It is not possible to delete ‘completion’ in Degreed via API. 

  • As it is not possible to delete ‘completion’ in Degreed via API, we are unable to remove any inaccurate ‘completions’ from Degreed. 

  • As it is not possible to delete ‘completion’ in Degreed via API, Degreed is unable to support Learn Amp’s recurring tasks. If recurring tasks are set in Learn Amp then required learning reporting in Degreed will be inaccurate (see scenarios below). 

  • It is not possible to created multiple Required Learnings for the same user + content combination via the API, even if they have different due dates. 

  • As it is not possible to created multiple Required Learnings for the same user + content combination via the API, even if they have different due dates, Degreed is unable to support Learn Amp’s recurring tasks. If recurring tasks are set then reporting in Degreed will be inaccurate (see scenarios below) 

  • NB. This is different to the behaviour of creating multiple ‘Assignments’ directly in Degreed. It is possible to have multiple Assignments for the same content and same user. This is not possible for Required Learning created through the API. 

Tasks and Required Learning scenarios

  • Learn Amp sends time and date of completion to Degreed, but it seems that Degreed removes the time from their side.

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
titleScenario 2: Content shows as ‘Completed’ in Degreed but ‘Not completed’ in Learn Amp.

There are multiple ways this scenario could occur: 

 

  • The content was manually uncompleted by the end user in Learn Amp.

    • It is possible for a user to ‘uncomplete’ some content types in Learn Amp. This will correctly cause the integration to remove the ‘verification’ in Degreed. When this happens, Degreed shows the associated Required Learning as ‘Complete.’

    • This means you will see a piece of synced content in Degreed marked as ‘Complete’ but marked as ‘Uncomplete’ in Learn Amp. 

    • As it is not possible to delete ‘completion’ in Degreed via API, we are unable to remove any inaccurate ‘completions’ from Degreed (we can only remove verifications via the API.) 

 

  • The content was ‘Marked Complete’ in Degreed by the user 

    • It is possible for the end user to ‘Mark Complete’ Courses that have been synced from Learn Amp. This will show the associated Required Learning as being ‘complete’ (NB. required learning will show as ‘verified’ when completed correctly on Learn Amp - see Defining Terms section above)

    • This is a ‘risk’ for customers that Learn Amp has no control over. For this reason, we recommend that customers use Learn Amp as the source of truth for compliance reporting. 

 

  • 'Require the user to complete this content again' was selected on a Learn Amp task

    • Learn Amp tasks have an optional setting called ‘require the user to complete this content again.’ If selected, it un-completes the content in Learn Amp; this is to allow for recurring tasks where users are required to complete the same content on a regular basis. 

    • If a user has completed content on Learn Amp (therefore now verified in Degreed), and is then subsequently set a task with this option selected for the same piece of content, Learn Amp will uncomplete the content, and the Required Learning will be marked as complete in Degreed.

    • As we are unable to remove ‘Completions’ via the API (we can only remove verifications) this is limitation in Degreed that Learn Amp cannot control.

 

  • Recurring tasks with the ‘require the user to complete this content again’ option selected 

    • Learn Amp’s recurring tasks cannot supported by Degreed as you cannot create two required learnings for the same user + content combination (see limitations + watchouts section)

    • But if a recurring task is set in Learn Amp with the ‘require the user to complete this content again’ selected, then when the task recurs…although a new required learning will not be created in Degreed, the verification will be removed, and the content will now show as complete in Degreed (similar the scenario above)

 

...

FAQs

Expand
titleWhy hasn't a required learning been created in Degreed?

  • The user/s and content outlined in the Task must also exist in Degreed for the Task to create a Required Learning.

  • Email is used to match users across Learn Amp and Degreed. If the email for the user does not match across both systems, a required learning will not be created.

  • If you assign a task to ‘new members’ of a company, team or group, then tasks are issued upon a user’s first sign into Learn Amp.

  • Please also refer to ‘Degreed Limitations and Watchouts’ section above.

Expand
titleHow often is data synced?

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
titleI’ve unarchived the only session on a Learn Amp Event, but I can’t see the Event or live event in Degreed

  • The only way to unarchive an Event in Learn Amp is via the 3 pips on the View Event page

  • If you have unarchived the Event Session from the Manage Event page in Learn Amp, you will then have to Unarchive the Event itself from the View Event page to see the Event + Live Event in Degreed 

  • This is due to a bug in Learn Amp. 

  • Once this bug is fixed, it is likely that unarchiving a session of an Event will unarchive the Event as well. 

  • This bug is not yet prioritised to be fixed. 

...