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.
SR-B32965 · Issue 294552
Agent minimum wakeup time changed to 1 second
Resolved in Pega Version 7.3
In order to allow sites to better customize agent schedules for picking up segments, the agent minimum wakeup time has been changed from 5 seconds to 1 second.
SR-B33088 · Issue 293375
pyGetAttachmentContent modified to access class for new properties
Resolved in Pega Version 7.3
The out-of-the-box properties IsDataPageRefreshed and PxAttachName were generating errors indicating the page contains undefined properties. The issue was with the activity pyGetAttachmentContent. As the properties pxAttachName and pyURL etc. are present in their respective classes and the data page class is Data- the errors were not visible. To correct this, pyGetAttachmentContent has been modified to use Page-Change-Class in the activity to change to the correct class so that properties can be accessed. pzRemoveAttachments and pzRefreshAttachmentList have also been updated to use pyIsDataPageRefreshed (new property created).
SR-B33387 · Issue 298483
Incorporated synchronized timestamp function for addWarning
Resolved in Pega Version 7.3
When the pxWarningCreatedDateTime was the same for two warnings with the same pxWarningName, one of the warnings was not getting justified. To fix this, the addWarning function will use the synchronized timestamp function getCurrentDateTimeUnique() to generate the created time.
SR-B33678 · Issue 292086
Bulk process with only 'case type any' properly assigns all processes
Resolved in Pega Version 7.3
When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.
SR-B33678 · Issue 292524
Bulk process with only 'case type any' properly assigns all processes
Resolved in Pega Version 7.3
When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.
SR-B33756 · Issue 295710
Updated logic check for property panel invalid actions
Resolved in Pega Version 7.3
Configuring invalid actions on the events & actions property panel was not triggering the validation messages when submitted, saved, and checked-in. When the action was re-opened, no changes were saved. This was due to a segment of code called on load of the property panel that remained for backwards compatibility but should not have been called in this scenario. This has been fixed by adding a check at the top of this activity for messages/errors which will route the logic appropriately.