Subscription Profile Repository (SPR) Release 9.1 Subscriber Provisioning Reference Manual Custom Fields — Custom fields are slightly different from entitlement fields, as they provide a place where you can store non-boolean data about a subscriber. As an example, let's assume that we wanted to store a bandwidth limit for a subscriber. We could do this by simply storing a value such as 1GB or 10GB in a custom field. There are some situations where it may not be clear whether you should use entitlements or a custom field to store data. Let's consider a situation where a subscriber may choose from 3 payment plans (P1, P2, P3) and we would like to represent the plan that was chosen.
One way to do this would be to put the payment plan into a custom field. Another way to do this would be to create entitlements such as "Plan:P1", "Plan:P2" and "Plan:P3" and represent it that way. Which option is better? In this case, the problem with representing this as entitlements is that it requires some extra maintenance when assigning values. This is because it is possible to associate two entitlements with a single subscriber, such as "Plan:P1" and "Plan:P2". However, this does not make sense, as this would mean that when you are setting the entitlement you need to make sure you remove the old entitlement, as well.
If you represented this as a single-valued custom field, then the act of assigning a new value would automatically overwrite the old value so the maintenance is simpler. The guiding principle for making the decision of how to represent subscriber data is simple - if the data can be represented as an on/off, or true/false, boolean-style piece of information then use entitlements. If it fits more naturally as a field-value pair, then use a Custom field instead. Subscriber Quota Name CLI: PolicyQuota WebCI: QuotaEntity XML-REST: quota Description The Subscriber Quota entity contains quota usage information related to a subscriber. Schema 261 910-6701-001 Revision A, June 2013