Engine Extensions
Check compatibility before adding an engine extension
Start an extension evaluation with the capability your engine needs.
By Globalesm
Start an extension evaluation with the capability your engine needs. Globalesm Engine Extensions cover areas such as access, change history, and clinical data. Availability and compatibility vary by add-on and engine version, so confirm the package and requirements with the team before installing.
Build the compatibility record
Capture the engine name, exact version, Java version, and related extensions already installed. Document where the add-on runs and who can install it. Ask whether signing or security-review prerequisites apply to your environment and which test conditions the package supports.
Prove the change in isolation
Install in an agreed test environment and run a representative channel or administrative task. Compare the outcome with your baseline. Verify what happens if the add-on is disabled or removed and whether recovery requires restoring configuration or restarting services.
Keep a usable handoff
Record the approved build, configuration, owners, and acceptance results. Confirm who reviews compatibility before the next engine upgrade. A versioned record makes it easier for the next operator to distinguish the engine’s behavior from the extension’s behavior.
Put the plan into practice
Tell us about the workflow, environment, and product capabilities you want to evaluate.