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

Query about Private Edit Functionality

SA-52880

Summary



The query is about the usage of 'Private edit' functionality in Production environment. User edited a report by doing a 'PrivateEdit' and save.
Intention was to have a personal copy of the report definition by doing 'private edit' however apparently it has affected the parent copy.


Error Messages

Not Applicable.

Steps to Reproduce

  1. Create Report Definition rule and check-in.
  2. Private edit the above created report definition

Root Cause



This is a query about the specifications and functionality of the Private Edit.

Resolution



It was explained, that private edit works only for the operator and the change will affect till we discard the rule.
Private edit functionality is managed by a role, so on the production level environment, the functionality is unavailable.
If we check priviledge pxAllowPrivateCheckOut, Private check out is allowed to upto Level 4 access for each rulesets.


Suggest Edit

Published March 14, 2018 - Updated October 8, 2020

Did you find this content helpful? Yes No

66% found this useful

Have a question? Get answers now.

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

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