Outcomes are results from user sessions.
Outcomes are typically sent to learning management system grade books but may be sent to any network endpoint in principle.
Pearson SCORM Services send the outcomes from sessions with SCORM media to a network end point if that web service is declared as one of the parameters in a Launch Request.
The Pearson SCORM Services Player app, in addition to being a SCORM Run Time Environment is factored as a remote Tool Provider as described in the IMS Learning Tools Interoperability (LTI) specification.This means that at the end of a session with SCORM media, the result of that session may be sent using LTI Basic Outcomes Services.
POST Outcomes API Details
Pearson SCORM Services send the outcomes from sessions with SCORM media to a network end point if that web service is included as one of the parameters in a a Launch Request.
To declare location for the outcomes two IMS Learning Information Services parameter name/value pairs need to be included in the a Launch Request:
The first of these parameters is a fully qualifed URL of the network web service endpoint. The second is an opaque identifier that is meaningful to the web service that receives the outcome message. The parameter name/value pairs are included in the Launch Request:
SCORM media has a life cycle within the Pearson SCORM Services Player app that starts by initating a communication session with a provided SCORM API Adapter and ends with a final commit of session state. These two boundary operations are described in the SCORM run time environment books as the SCORM API Session methods:
When the API.Terminate Session method is invoked, the Pearson SCORM Services enter the following workflow:
- The API.Terminate operation sends the session state (possibly including grade/score information) from the Player app to Pearson SCORM Services.
- The Pearson SCORM Services persist the session state
- If grade/score information is included in the session state (as a cmi.score.scaled value) then an XML message is sent to the web service endpoint that was declared as the value to the lis_outcome_service_url paramter in the Launch Request.
The XML message that is sent to the web service endpoint that was declared as the value to the lis_outcome_service_url paramter in the Launch Request is factored as the request body of an OAuth signed HTTP POST request. The XML contains both the value of the lis_result_sourcedid paramter from the Launch Request and the cmi.score.scaled value from the SCORM session state. An example XML request body is shown below:
<?xml version="1.0" encoding="utf-8" ?> <imsx_poxenveloperequest xmlns="http://www.imsglobal.org/services/ltiv1p1/xsd/imsoms_v1p0"> <imsx_POXHeader> <imsx_POXRequestHeaderInfo> <imsx_version>V1.0</imsx_version> <imsx_messageIdentifier>999999123</imsx_messageIdentifier> </imsx_POXRequestHeaderInfo> </imsx_POXHeader> <imsx_POXBody> <replaceResultRequest> <resultRecord> <sourcedGUID> <sourcedId>feb-123-456-2929-28883</sourcedId> </sourcedGUID> <result> <resultScore> <language>en</language> <textString>0.92</textString> </resultScore> </result> </resultRecord> </replaceResultRequest> </imsx_POXBody> </imsx_poxenveloperequest>
The XML message format is defined in the OMSv1p0_LTIv1p1Profile_SyncXSD_v1p0.xsd schema that is available
Full details of the IMS LTI 1.1.1 Launch Request and Basic Outcomes Services are available