Intelex configuration9 min read

Enhesa Gateway in Intelex: what lands, and what you build

Intelex sells the Regulatory Content Gateway as the way to "combine regulatory content from Enhesa and RegScan" with its compliance applications, drawing on "regulatory information from over 140 global jurisdictions." Enhesa's own site says it covers 400 or more jurisdictions. Nobody explains the difference, and that is roughly the state of public documentation for the whole integration: two vendor pages, two numbers, and nothing at all about what the content looks like once it is inside your environment.

This article is about that receiving side, because it is the side you configure. How the gateway connects, authenticates and syncs is deliberately not covered. Those screens are specific to each environment and are not drawn on here. What follows is the shape of what arrives, the three things you must have in place to catch it, and the one step people skip that leaves an applicability study looking broken when it is merely empty.

It lands in the object you already have

The most useful single fact is that the gateway does not bring its own data model. The Enhesa Requirements inventory is a custom inventory view, and the platform warning it displays names the object underneath: