Tracking Registration Results

Technically, Engine does all the tracking for you, but Engine doesn't have any idea what you intend to do with the data it captures. As discussed in the overview, your system should store its own version of the registration state to display to the user in your application and for other reporting purposes. We provide a couple of ways of keeping that data in sync with the registration state in Engine.

Automatic Postbacks

Engine can be configured to send postbacks to an endpoint in your system (webhook) whenever it receives an update to the status of one of your registrations.

To configure this, set the value for ApiRollupRegistrationPostBackUrl to the URL of the endpoint in your application you've built to listen for the postbacks. Once you've done that, Engine will POST a JSON object describing the status of a registration to your application whenever it receives an update from the player about an in-progress course launch.

These postbacks will be of the same schema that is used by the API. To make it easier to handle the postback coming from Engine, you can reference the API client's classes. You can translate the body of the postback into a RusticiSoftware.Core.api.client.v2.Model.RegistrationSchema using your favorite JSON parser.

Note for legacy integration customers: If you want to switch to using Engine's automatic postback functionality, then you will need to make some slight modifications to your integration class. Your integration layer should be changed to inherit from RusticiSoftware.Engine.api.implementation.BaseApiIntegration instead of DefaultIntegration. Our BaseApiIntegration provides its own implementation of RollupRegistration that handles the automatic postbacks, so you will need to remove your implementation of that method.

Postback Configuration

There are a few settings that allow you to configure the behavior of Engine's automatic postbacks. The only setting required to enable the automatic postbacks to your system is ApiRollupRegistrationPostBackUrl, but you can set any of the following to further customize the behavior.

  • ApiRollupRegistrationFormat: The level of detail in the information that is posted to you. It may be one of three values: course (course summary), activity (activity summary, the default value), or full (all detail available). If you are only reporting on top-level details (like completion, success, score, duration), then we recommend that you set this value to course to minimize the amount data that has to be POSTed from Engine to your application.

  • ApiRollupRegistrationAuthType: Indicates how to authorize against the given postback URL. You can specify either form or httpbasic, with httpbasic as the default value. If form authentication, the username and password for authentication are submitted as form fields username and password, and the registration data as the form field data. If httpbasic authentication is used, the username and password are placed in the standard Authorization HTTP header, and the registration data is the body of the message.

  • ApiRollupRegistrationAuthUser: Username to use when posting registration data.

  • ApiRollupRegistrationAuthPassword: Password to use when posting registration data.

Postback Frequency

By default, Engine's SCORM player does not immediately save data committed by the content. Instead, it checks for dirty data on a set frequency (every 10 seconds), and if any is found, it sends it back to Engine to save in the database. Whenever Engine receives these updates, it will trigger the automatic postbacks to your system mentioned above.

Some customers have found this to happen a bit too frequently, increasing the load on Engine, and also on their own system to process the registration postbacks. To combat this, you can turn down the frequency at which the player checks for dirty data during the launch, as so reduce the frequency of possible postbacks to your endpoint.

To adjust this frequency, add an entry in your Engine config file for PlayerCommCommitFrequency, and give it a value higher than the default of 10 seconds. The value should be in milliseconds, so you will want to change its value to something like 30000 or even 60000. You should be careful, though, not to set this value so high that the player posts back too infrequently. If anything happens that would unexpectedly cut the learner's connection to Engine, the learner will lose all of the progress they've accrued since the last time the player sent an update. You will want to find a sweet spot between minimizing server load and ensuring the safety of your learners' progress.

Querying the API

At any time, you can retrieve the current state of a registration using the /registrations/{registrationId} endpoint. This endpoint will return the same JSON schema that you receive in the registration postbacks. You might use this as a way to manually refresh a registration's state when needed.

Please remember that these resources are not intended to be ad hoc reporting mechanisms. Fetching all of the information about the registrations is not a small task, and repeatedly hitting these endpoints can result in negative effects on Engine's performance.

When calling the /registrations endpoint, there are a few parameters that control how much detail about the registration is returned:

  • includeChildResults: this includes details about each activity or learning object in the course, not just the top-level summary
  • includeRuntime: includes the runtime data of the activities
  • includeInteractionsAndObjectives: this goes a step further and includes objective and runtime interaction details (questions/answers)

We disable these parameters by default, as each one adds additional processing time for creating the result. Many customers only care about the top-level details anyway, so this lets you include them only if actually needed.

Resetting Learner Progress

There may be times when you need to reset a learner's registration state so that they basically start over fresh. This may be so the user can retake the course, or to clear out data during testing. You can trigger this clearing of progress data by doing a DELETE request to the /registrations/{registrationId}/progress endpoint.

results matching ""

    No results matching ""