Integrating Custom Entitlement Solution

It is quite possible that for the solution that is being put together there is already an existing entitlement service that is sought to be used. In such a case, the following needs to be kept in mind:

• The Product, Sub Product and Function attributes that are to be configured across the various layers of Canvas are to be interpreted and mapped to the third party entitlement setup.
  • There are multiple approaches to solve this:
    • There can be a mapping table that helps convert any linear entitlement setup into the hierarchy setup of Canvas.
    • One or more of the hierarchies can be assigned or defaulted during the configuration across Canvas. These hierarchies can be effectively nullified during the entitlement implementation callbacks.
• The implementation callback is treated as a use and throw object and it is the framework's decision on how many and when it creates the instance. So, any implementation should not try to maintain any state within their implementation. Canvas does not attempt to maintain the state within or across the sessions.

View the following Pages