SR-C83808 · Issue 421299
FIRST aggregate in bucketed window fixed
Resolved in Pega Version 8.1.3
FIRST aggregates were not giving the correct results if used in a Sliding Time window together with an average aggregate.This was traced to an incorrect implementation of FirstAggregatorHolder.substractAggregate which used propertyIndex to get aggregate value (which was not correct in this context), and has been fixed by using the correct index in FirstAggregatorHolder class.
SR-C83915 · Issue 421169
Enhancement added to support property reference name for section include
Resolved in Pega Version 8.1.3
When requesting the view of a section from a repeating dynamic layout where the name of the section is taken from a property, the DX API returned an error on the tracer indicating "Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getString(String)". This has been resolved by adding an enhancement to support using a property reference for section include.
SR-C85035 · Issue 421948
Added getIfPresent check for Field Value parameters with pzAPICreateJsonForView
Resolved in Pega Version 8.1.3
Calling pzAPICreateJsonForView was altering case values if localized field value parameters were added. This has been corrected by performing a getIfPresent and getIfString on the property pyFieldValueParams so field value parameters will not be added to the main page if they're not present.
SR-B71423 · Issue 319981
Localization added to pyAccountSettings field labels
Resolved in Pega Version 7.4
Field label localization for the pyAccountSettings section rule has been added to the Pega-IntegrationArchitect ruleset.
SR-B54277 · Issue 336406
Trimmed unneeded properties from doUIAction call
Resolved in Pega Version 7.4
Null pointer exceptions were generated when relaunching the manager portal after saving a work-object, and the error "Request-URL Too Large. The requested URL's length exceeds the capacity limit for this server" appeared. This was traced to the number of properties included in the doUIAction call; unnecessary parameters have been removed to resolve this issue.
SR-B66164 · Issue 325166
Handling improved for pzActiondropdown's Action label value
Resolved in Pega Version 7.4
When an alternate flow action was picked from LocalAction's list and then submitted, the presence of any page-set messages would cause the submission to fail and the flow remained on the same flow action. This was an issue with handling the changed value of the FlowAction label, and the pzActionDropdown control has been modified to get the correct pyDefaultActionIndex parameter value.
SR-B70422 · Issue 326897
Removed unnecessary add/delete history entries related to empty page properties
Resolved in Pega Version 7.4
The field level auditing configured for page group or list property types was creating multiple add and delete entries in the history of the case even though the pagelist/pagegroup had not been modified. This was traced to method used by the pagelist change audit process to compare current pages to the previous value of the pagelist pages: during pagetostring conversion, sometimes the empty properties in page are present in the String and sometimes they are not, resulting in a difference that generated the non-essential audit entries. This has been fixed by changing the getProperty references in getPageAsString function to use getIfPresent instead. Null checks have also been added.
SR-B70595 · Issue 328754
Out of box REST API creates Page Lists with pxObjClass
Resolved in Pega Version 7.4
Page-Merge-Into was implemented in such a way that the pxObjClass was added for a page but not for a Page List until the case was created. This interfered with validating pagelists and identifying problems with the message data that would allow the case to be rejected before creation. To allow for more flexibility, the pzCreateCaseInternal activity contains an added a property-set so that the pxObjClass is updated on embedded pages.
SR-B74583 · Issue 325617
SendEmail smart shape fixed to populate PartyRole correctly
Resolved in Pega Version 7.4
Due to issues with populating the pxPartyRole property, emails were not being sent to all members in a repeat party after upgrading. This was traced to a missing call in the modified SendEmail smart shape, and has been fixed.
SR-B75096 · Issue 329151
Bulk actions filter clears previous value
Resolved in Pega Version 7.4
When running Bulk Actions, attempting to delete filter conditions was resetting clipboard values and no results were displayed. This was an unintended consequence of changes that retained pyUserIdentifier on the conditions page even when "Assigned to Operator" was not in the filter list. To correct this, it will be removed when pyUsage is not equal to Operator.