Posted: 13 Oct 2015 12:13 EDT Last activity: 29 Oct 2015 10:12 EDT
SSO dont work after upgrade to PRPC7.1.7
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.
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.