Calyx RIM 6.2 Release Notes

List of Enhancements: Calyx RIM 6.2 CHF 1

Requested new features and enhancements are included in each release. The items are listed in descending order by their tracking numbers. Customer case numbers that were recorded when the enhancements were requested are included in brackets [#####] following the tracking number.

Calyx RIM 6.2 CHF 1 includes the following enhancements.


Issue	Build	Hotfix Build	Description
25746; [00058184]	6.2.0.1.0004	N/A	When you use the Veeva Vault, the number of requests sent to Veeva by Calyx RIM is limited by the number that is defined by the Veeva System. Calyx RIM 6.2 CHF 1 leverages the Veeva Bulk API calls with an internal cache. This will decrease the chance of encountering 5-minute API burst restrictions imposed by Veeva Vault. The optimal cache lifetime depends on one of the following factors: Optimizing the number of Veeva requests (the higher the Veeva objects cache timeout value, the fewer InSight API calls to Veeva) Keeping the data up-to date Keep in mind that setting the Veeva cache timeout to a higher value will reduce the number of Veeva requests. However, this can also lead to a risk of getting data that is not relevant.

JavaScript must be enabled in order to use this site.Please enable JavaScript in your browser and refresh the page.

List of Enhancements: Calyx RIM 6.2 CHF 1

Requested new features and enhancements are included in each release. The items are listed in descending order by their tracking numbers. Customer case numbers that were recorded when the enhancements were requested are included in brackets [#####] following the tracking number.

Calyx RIM 6.2 CHF 1 includes the following enhancements.


Issue	Build	Hotfix Build	Description
25746; [00058184]	6.2.0.1.0004	N/A	When you use the Veeva Vault, the number of requests sent to Veeva by Calyx RIM is limited by the number that is defined by the Veeva System. Calyx RIM 6.2 CHF 1 leverages the Veeva Bulk API calls with an internal cache. This will decrease the chance of encountering 5-minute API burst restrictions imposed by Veeva Vault. The optimal cache lifetime depends on one of the following factors: Optimizing the number of Veeva requests (the higher the Veeva objects cache timeout value, the fewer InSight API calls to Veeva) Keeping the data up-to date Keep in mind that setting the Veeva cache timeout to a higher value will reduce the number of Veeva requests. However, this can also lead to a risk of getting data that is not relevant.