Program records are how learners can view and share their achievements in a given program.
There is now a Learner Records Microfrontend that can be used in in place of the legacy credentials UI. The records MFE provides all the same features of the credentials views, with a few changes. Mainly, it no longer supports masquerading, and instead uses a new tab created in the Support tools MFE for tasks that would be completed using masquerading in the past. In the future, the credentials views will be deprecated with the MFE in its place. Eventually the old views will be removed entirely.
To have the UI link to the new MFE, the flag
LEARNER_RECORD_MICROFRONTEND_URL must be set for both the LMS and the profile MFE if it is in use. This flag is defined in the base.py file in credentials settings.
A learner can see a list of their own program records at
/records/ which then links to specific program records under
If you are a staff user, you can masquerade as a specific learner (see the pages as that user sees them) by using the banner that appears at the top of the records pages.
A learner must be logged in to view these pages.
The list of records is linked to from the LMS under each learnerʼs profile. Each specific program record is linked to from the LMS under that programʼs progress dashboard page.
Program Records donʼt have a concrete representation in the database. Rather, the view for a record is created when the LMS tells the Credentials IDA that a course certificate has been awarded in a program. That — plus grade information (also sent by the LMS) — gets used to display records pages to the learner.
Records are enabled by default.
But you can disable support for the records feature by toggling the
Enable Records checkbox in a given site configuration.
This will disable the views from appearing and will stop the
copy_catalog job from saving catalog data for that site.
Additionally, you will want to disable a similar site configuration toggle on the LMS side, so that it will stop sending records data to Credentials.
Also make sure that the
copy_catalog job is run periodically.
It pulls in all the required program catalog data from the Discovery IDA.
If for whatever reason, you need to backpopulate records data (maybe there was a service outage, or you just enabled records support for a site), you will want to run the LMS management command
Look at its LMS documentation to see your options.
A learner can also choose to send the record to a site partner, to receive credit from that partner for the earned certificates.
Note that this merely sends an email to the partner so they can see the record. Each partner will have their own process for initiating or processing a credit request, of which viewing a learnerʼs record is one small part.
Read the pathways documentation for more information on how to enable and configure requesting credit.
If no credit pathways are enabled for a given program, the
Send Learner Record button will not appear on that programʼs records.