Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

pyTrackSecuritychangesModel is not created

SA-16356

Summary



pyTrackSecuritychangesModel is not created after clicking Submit button in Process and Rules: Work Management wizard > Field Level Auditing.

After clicking Submit, the property disappears from the list.



Error Messages



No error message in the screen. In tracer there are errors like below:

** Create new record failed: .pyModelName: The rule name pyTrackSecurityChanges is a reserved name (starts with px, py, or pz) and is not created in a "Pega-" ruleset
.pyRefToFocusKey: The rule name pyTrackSecurityChanges is a reserved name (starts with px, py, or pz) and is not created in a "Pega-" ruleset.


Steps to Reproduce

  1. PegaButton > Process&Rules > Work Management > Field Level Auditing
  2. Select Case or Supporting Type as needed for Work class
  3. Add a property
  4. Click Submit


Root Cause



A defect in Pegasystems’ code or rules.

Resolution



Upgrade to Pega 7.1.9.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us