How to report widget scores in Outcomes Report?

updated 2 wk ago
1reply

Widget Score Reporting is a capability that lets the platform capture granular, itemised scores from widgets — not just a single overall number. For example, a code submission post can now report separate scores for "Unit Tests," "Linting," and "Stress Tests" instead of lumping everything into one grade.

These individual scores (called score items) can then flow into assessments, reducing manual data entry for facilitators and giving institutions richer insight into learner performance.

Assessment Designers can map a specific score item to a criterion in an outcomes report.

What is a "score item"?

A score item is a single scorable dimension within a widget. Think of it as one row in a marking rubric that gets its score automatically.

For example, a Post widget with the code execution integration might have three line items:

Functional Correctness Tests — out of 10
Stress Test — out of 10
Code Linter Report — out of 100

Each line item has its own name, maximum score, and value per learner.

What are Core, Custom, and Detected line items?

These are the three ways a line item can come into existence:

Core: The default, primary score that every widget has out of the box (e.g., "Overall score" for a Post widget). It's always there; course authors don't need to set it up.
Custom: A line item that a course author creates ahead of time by telling the system what to expect (e.g., "I know my webhook will send a field called 'Unit Tests'").
Detected: A line item the system creates automatically when it receives a score it hasn't seen before. It just appears — no setup required.

If a course author later edits a Detected item (renames it, changes the max score, etc.), it gets promoted to Custom and stays that way.