SR-B2709 · Issue 275299
Resolved ConcurrentModification exception in getclass name
Resolved in Pega Version 7.3
Attempting to getclass name while iterating over values of mPageProperties in expandAllToProperties (in the putPropertyOntoClipboard call) was causing a ConcurrentModificationException that resulted in queues being blocked and loss of synch to the server. In order to more cleanly set the pxObjClass for the classless page-properties, pxObjClass has been added to the lookupDictionaryDefinition.
SR-B30914 · Issue 290290
PurgeExtraRecents logging changed from error to info
Resolved in Pega Version 7.3
In order to support increasing the number of recent items to display to more than 30, the existing logging function in System-User-Recents!pzPurgeExtraRecents activity has been changed from error mode to info mode so the logging can be disabled if desired.
SR-B30962 · Issue 291933
SaveOperatorUnavailability error message made generic
Resolved in Pega Version 7.3
Data-Admin-Operator-ID.SaveOperatorUnavailability generates the error message ("You are not authorized to create, modify, or lock operator instance "+myStepPage.getString("pyUserIdentifier")); if the request is not sent with the proper privileges. In order to obscure what the privileges are from potentially malicious use, this message has been made more general with the text "You are not authorized for this operation".
SR-B31667 · Issue 289067
Consistent Work IDs between case types created in different implementations
Resolved in Pega Version 7.3
Creating an Implementation layer on the Warranty application using the New Application wizard of Pega 7.22 GA was resulting in a different Work ID prefix of some case types like Claim Unit or Appeal than when the same case types were created in the built on application. This was traced to different activities being used to populate the data page, and has been updated to ensure uniform work ID generation.
SR-B3208 · Issue 293911
Check added to ensure Tracer finds regular pages
Resolved in Pega Version 7.3
Page D_Properties was mentioned in pages to trace, it was present in clipboard, but was not passed to tracer due to an error in page handing. An extra check has been added as a fallback to look for a regular page if Tracer's data page check does not return a named page.
SR-B3208 · Issue 294773
Dot added to Rule Reference filename in Help
Resolved in Pega Version 7.3
The Rule Reference help file has been updated to insert a dot in the filename: "When you save a rule, the standard Declare Index rule named Rule-.RuleReference updates this table to reflect the references in that rule to other rules."
SR-B32247 · Issue 291773
Resolved null-pointer exception at ReferencePropertyLinkToCommonParent
Resolved in Pega Version 7.3
When a reference property (liked via top level page) was copied with-in the page (intrapage), an null-pointer exception would be generated by a bad link if the number of levels in the new property differed from the original. The issue was traced to an error in the After Copy duplicator that did not correctly evaluate the target property in all environments. More robust testing has led to refinements on the duplicator to resolve this issue.
SR-B32618 · Issue 289713
BLOB handling improved for empty properties in HistorySaver
Resolved in Pega Version 7.3
In HistorySaver, using ClipboardProperty.setValue to save snapshot data for the previous version of the rule had the side effect of stripping blank properties from the clipboard page. This caused rules relying on these properties to not be restored correctly. To correct this, special handling has been inserted for the instances History- class and its descendants to serialize blob with EmptyProperties.
SR-B32618 · Issue 276417
Enhancement added to maintain blank properties when using History Snapshots
Resolved in Pega Version 7.3
In HistorySaver, using ClipboardProperty.setValue to save snapshot data for the previous version of the rule had the side effect of stripping blank properties from the clipboard page, and so any rules that rely on these properties would not be restored correctly. To resolve this, an enhancement has been added to specially handle instances History- class and its descendants to serialize blob with EmptyProperties.
SR-B32618 · Issue 276417
Enhancement added to maintain blank properties when using History Snapshots
Resolved in Pega Version 7.3
In HistorySaver, using ClipboardProperty.setValue to save snapshot data for the previous version of the rule had the side effect of stripping blank properties from the clipboard page, and so any rules that rely on these properties would not be restored correctly. To resolve this, an enhancement has been added to specially handle instances History- class and its descendants to serialize blob with EmptyProperties.