Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 ChandraSekhar Bhagath Vasireddy (BhagathVasireddy)
JPMC

JPMC
US
BhagathVasireddy Member since 2013 2 posts
JPMC
Posted: Oct 13, 2015
Last activity: Oct 29, 2015
Posted: 13 Oct 2015 12:13 EDT
Last activity: 29 Oct 2015 10:12 EDT
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

To see attachments, please log in.
Security

Posted: 9 years ago
Posted: 29 Oct 2015 10:12 EDT
Luigi Leo (leo_l)
PEGA
Engagement Strategy Content Expert & Sr. Principal Instructor
Pegasystems Inc.
US

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

To see attachments, please log in.

Related content:

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice