Question
AIG
US
Last activity: 21 Jul 2017 10:32 EDT
OCX Controls are backward Compatible ?
Please confirm that later versions of OCX controls (specifically PRPC71ml6) are compatible with earlier versions of PRPC (specifically PRPC62sp1) ?
***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
US
I will expand on the Gaurav’s reply.
PRPC ActiveX controls are maintained to be binary-compatible across all PRPC versions, but functional compatibility is not guaranteed.
Binary compatibility means that older versions of public API’s have signature (method name and parameters) identical to those of the newer version, allowing controls from other versions of PRPC releases to successfully get loaded.
As for functional compatibility, Pega makes maximum effort to maintain it from release to release, but sometimes it is impossible due to evolution of the supported functionality.
Engineering QA does not test for ActiveX functional compatibility across releases! Therefore, the recommended best practice is to set of ActiveX controls fully matching the particular PRPC release.
Nevertheless is it possible in many cases to use controls from newer PRPC version with an older version, but the customer is responsible for testing.
A general observation: the more distant PRPC releases are the less likely controls will be functionally compatible between them. So, in the Ashok’s specific example (Pega 7.1.6 vs PRPC 6.2 SP1), the version difference is far too great to expect compatibility.
Pegasystems Inc.
IN
Hi Ashok,
The OCX controls of the later versions are not compatible with earlier versions of PRPC. The OCX control for each version of PRPC are been shipped with the base Product itself and its got evolved with the new Internet Explore evolution with new features added and old removed.
Thanks
Accepted Solution
Pegasystems Inc.
US
I will expand on the Gaurav’s reply.
PRPC ActiveX controls are maintained to be binary-compatible across all PRPC versions, but functional compatibility is not guaranteed.
Binary compatibility means that older versions of public API’s have signature (method name and parameters) identical to those of the newer version, allowing controls from other versions of PRPC releases to successfully get loaded.
As for functional compatibility, Pega makes maximum effort to maintain it from release to release, but sometimes it is impossible due to evolution of the supported functionality.
Engineering QA does not test for ActiveX functional compatibility across releases! Therefore, the recommended best practice is to set of ActiveX controls fully matching the particular PRPC release.
Nevertheless is it possible in many cases to use controls from newer PRPC version with an older version, but the customer is responsible for testing.
A general observation: the more distant PRPC releases are the less likely controls will be functionally compatible between them. So, in the Ashok’s specific example (Pega 7.1.6 vs PRPC 6.2 SP1), the version difference is far too great to expect compatibility.
Pegasystems Inc.
US
Might this PDN Article be of interest?
PRPC ActiveX controls are not compatible with 64-bit versions of Internet Explorer
https://pdn.pega.com/node/2044
It explains differences between PRPC 5x, 6x and Pega 7 OCX support with Internet Explorer and links to the PDN Articles for Pega 7:
Client-side technologies in Pega 7.1.1 - 7.1.7
Client-side technologies in Pega 7.1.8
https://community.pega.com/support/support-articles/rule-change-not-updated-all-nodes