Operator guideENnxgamesrelations

NX / Games / Restriction Mapping

Relation page for linking one NX game to country or market restrictions.

Reader view

Clean portal guidance

This page keeps the operator explanation, field and action descriptions, and screenshots visible without exposing repo paths, raw sidecars, or editorial-only implementation details.

Narrative content

Page body

What this page does

This page manages which restriction records are mapped to one NX game.

When to use it

check where a game is blocked by market or country restriction
add or remove restriction mappings for one game
confirm whether the relation is scoped to casino or external visibility

Known caveats

Restriction mapping is separate from category and currency mapping.
Scope matters. The same restriction code can behave differently depending on the selected restriction scope.

Field dictionary

Fields

field

Related record

Represents the FE-visible related record managed from this relation surface.

Data Type: string
Caveats: This is a minimal dictionary entry added to close the current coverage-audit gap., Expand this sidecar with exact FE labels and payload mappings during the next module pass.

Operational notes

Notes

item

FE relation page is mapped from the NX game workspace.

item

Restrictions are served and mutated through the core mapping factory with explicit restriction scope parameters.

Related references

pageNX / Games

Operator guide for NX game list, record detail, mapping relations, restriction mapping, and ordering workflows.

pageNX / Games / Category Mapping

Relation page for linking one game to categories.

pageNX / Games / Currency Mapping

Relation page for linking one game to currencies.

pageNX / Games / Detail

Record-level workspace for one NX game.

pageNX / Games / List

Main NX games grid with filters, provider context, and reorder entrypoint.

pageNX / Games / Reorder

Ordering screen for NX games.