Send Exam Eligibility to Prometric Behavior

Owned by Seth Petry-Johnson
Last updated: Jan 02, 2023 by Nadine Burroughs

See https://heuristicsolutions.atlassian.net/wiki/spaces/DOCS/pages/3413966876 for usage information.

Prior to 11.0.17 this was called “Send Test Authorization to Prometric GEE”

Overview

This behavior sends “authorization to test” notifications into Prometric’s “Generic Eligibility Engine” [GEE] system.

Behavior configuration

Usage Instructions

The “Prometric Legacy Behavior” option (see screenshot above) was deprecated in 11.0.15.

This option uses the Integration Hub to proxy the API payload from LearningBuilder into Prometric and was replaced by the “HTTP API Call” option that no longer needs the Integration Hub.

This Behavior requires that two elements already be configured:

  • A “System Template” that describes the XML payload to send to the GEE

  • An “API Endpoint”, which is where that XML payload is sent

The Behavior itself can be configured by a normal administrator, but those prerequisites must be set up by a Sys Admin.

See https://heuristicsolutions.atlassian.net/wiki/spaces/DOCS/pages/3414654979

Assuming that the API Endpoint and System Template are already configured, all you need to do is select them in the relevant dropdowns.

All of the mapping between LearningBuilder elements and Prometric elements (e.g. exam codes, eligibility IDs, etc) happens in the template.

Note: This Behavior is “re-runnable”; it can be called multiple times with the same information without errors or negative consequences.

Troubleshooting

This Behavior logs to the BEHAVIOR_EVENT table. If it fails to run it should log a reason there.

Common errors include:

  • Malformed template (most often a configuration error but could be a data error)

  • Unable to access endpoint (most often a configuration error)

  • Invalid request (Rejected by endpoint because the data broke rules defined by Prometric)

The actual message that was sent (e.g. the rendered template) is logged in Cloudwatch.