When you modify a rule instance, you can save your changes to a higher numbered versions of the RuleSet with impacting the current version.
-
True
-
False
When modifying a rule instance in Pega PRPC, you can save changes to a higher-numbered version of the RuleSet without affecting the current (lower-numbered) version. This versioning isolation allows controlled evolution of rules while maintaining stability of existing implementations.
In Pega (PRPC), RuleSet versioning is explicitly designed so that saving a modified rule instance into a higher-numbered RuleSet version does NOT alter or impact the currently active/lower version of that rule. The lower version remains untouched and continues to be used by any application still pointing at it; only applications that reference the new higher version pick up the change. This is the entire point of ruleset versioning — safe, non-destructive iteration. The question statement, read with the obvious typo corrected ('without impacting the current version' instead of 'with impacting'), is describing exactly this designed behavior, so the true statement should be marked True. The DB's marked answer of False is a straightforward casualty of not correcting for the typo when grading, but the underlying assertion (once fixed) is a true statement about Pega versioning.