Sections in the Article
Note! The Extension Id of the Custom CVL in the Control Center must exactly match the CVL Id in the data model. Otherwise, the Custom CVL will not be associated with the CVL in the model.
Note! Since a Custom CVL is populated from an external source it does not "exist" as a traditional CVL. This means CVL Listeners will not receive events (Connect Messages) pertaining to the Custom CVLs.
You can choose this option if the source of the CVL values is elsewhere than in the data model. In a standard inRiver implementation, there are for example two predefined Custom CVL extensions for the CVLs Users and GroupTask. The values of these CVL:s are managed by extensions that get the data from the inRiver user list and role list respectively.
When you use the CVLs in your applications you see no difference between a normal CVL and a Custom CVL.
Custom CVL in Control Center
You create the CVL in Control Center and check the property Custom Value List. That tells the system that it should look for a code extension managing the CVL values.
Building a Custom CVL Extension
For the Custom CVL to work, you must build and install an extension. In this extension, you implement an interface called ICustomValueList. The interface is available in the remoting API.
Read more about how to work with a custom CVL extension in this article.