Entitlements are a type of product that enables or disables specific functionality for a subscriber. Like with plans, entitlement products require policies, and an entitlement product requires an entitlement policy.
An entitlement policy requires an entitlement code. An entitlement code defines what network behavior the entitlement policy allows. The entitlement codes that you can add to entitlement policies depend on what your network integration allows, and can include bucket IDs and service offer codes (SOCs). Contact your administrator for more information.
An entitlement policy does not require a component, although one (or more) can be added. However, if you want to send intercept notifications to your subscribers when they request entitlement services that are not enabled, and if your network does not send entitlement codes to the ItsOn Service Design Center system, then you must add a component to the entitlement policy. The filters in the component should match the entitlement code in the entitlement policy. The filters identify when subscribers request entitlement services that are not enabled, which can trigger intercept notifications. Those notifications can encourage the purchase of entitlement products that enable the requested services.
Unlike service policies and service eCommerce policies, entitlement policies do not require components before they can be tested and published. Also, components in entitlement policies do not contain policy events. (Policy events define the "where" and "when" of service policies, and neither of those are required for entitlement policies because entitlement policies only enable or disable functionality.)
You can: