The Entitlement policies that build items, such as the Group_Values MAP object, are slow and resource intensive when the number of groups exceeds just a few thousand. This not only stops other time critical transactions from occurring, but results in CODE MAP REFRESH timeouts and the data never becomes available to the User Application.
Two stages to allow migration/coexistence:
Stage 1: Create an "entitlement thread" within the engine that simply responds to query documents from the CODE MAP REFRESH call, does not get processed by policies, and allow the CODE MAP REFRESH to be scheduled (time of day as well as frequency) per entitlement.
Stage 2: Allow configuration of entitlement value "filters" for the query that CODE MAP REFRESH initiates within the User Application interface - "decoupling" the reliance on the driver specific code from User App and centralising the Entitlement process.