...
Note: This is the default table provided by Canvas to define the entitlement criteria. You can use your own entitlement criteria definition table. However, you must make necessary changes in the EntitlementsHelper class for the framework to read the table.
Data level entitlement criteria must be defined in this table. Canvas expects that the data level entitlements are mapped to the Product – Sub Product combination and not directly to functions. This goes with the concept that all functions under a Product – Sub Product combination automatically derive the data level criteria applicable. There could be scenarios where a function may not work with any data level criteria. In such cases, the function could be marked as read-only to indicate that scenario.
Following is a sample screen shot of how the entries can be provided in the OO_CRITERIA_TYPE_MASTER table:
Column Name | M / O | Type | Purpose |
---|---|---|---|
CRITERIA_TYPE | M | String | The criteria type (key) against which the data level entitlement is captured as part of profiling. |
DESCRIPTION | O | String | This is a column provided to the developer for storing any meaningful comment for quick identification of the entitlement criteria. For example, Loan type criteria. |
SOURCE_TYPE | M | String | Indicates how the possible values for the criterion can be fetched. The default source type is V.
|
SOURCE_VALUE | M | String | Provides the actual value corresponding to the source type. |
PRODUCT_CODE | M | String | This is the product code that is recognized by Canvas and is used as part of its internal storage of profiles, etc. |
SUBPRODUCT_CODE | M | String | This is the sub product under the provided product that is to be used. This is the code that is recognized by Canvas and is used as part of its internal storage of profiles, etc. |
...