Core
Lynx Licence Enforcer - Website Bridge
Applies the enforcer Apps filter to the website Add Features list
lynx_license_enforcer_website
· v19.0.1.0.0
What this solves
Lynx Licence Enforcer - Website Bridge
Thin glue between lynx_license_enforcer and website. It defines no model of its own and carries a single record: the domain override on website.action_website_add_features.
Key Features
Consistent Apps filtering — the "Add Features" screen hides modules in state uninstallable, exactly as the enforcer already does for the main Apps list.
No payload of its own — no model, field or view is defined here, so the bridge can be uninstalled without touching enforcement.
Absent on tenants without a site — the override targets a website record, so it only exists where that record does.
Auto-Installation
This module is auto_install. The record it carries overrides an xmlid owned by website, which lynx_license_enforcer does not depend on — declaring it there makes the enforcer fail to load on every tenant without a site. Keeping the override in a bridge means it applies exactly when both modules are present and never otherwise.
Depends on
Try Lynx Licence Enforcer - Website Bridge on your team.
Free trial, no credit card. Talk to sales when you're ready.