Discussion
1
Replies
126
Views
JPMC
Posted: October 13, 2015
Last activity: October 29, 2015
Closed
SSO dont work after upgrade to PRPC7.1.7
ROOT CAUSE
In PRPC 7 ML7 the functionality of Tracking changes on a data instance is broken as the function that writes the history record uses a new property called pyPropertyIndex (which is a String instead of an Integer as you would expect). The property only exists in Embed-ModelParams class and not @baseclass so for an Operator record (Data-Admin-Operator-ID) it would not find it. The operator record is however initially saved. The operator record cannot subsequently be changed as validation fails when it sees this property on the operator top-level page.
RESOLUTION
HFix-20074
Regards,
Chandrasekhar Bhagath, Vasireddy
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion.
In order to resolve the issue that you are experiencing a thorough review of all of the factors contributing to the issue is required. Please submit a Service Request (SR) so that one of our Customer Support technicians can work with you on this. You can do so by contacting Pegasystems Global Technical Support through My Support Portal.
The PDN Forum Support Team,
Lu