SR-B30403 · Issue 290587
Layout group contents now load fully during a tab overflow
Resolved in Pega Version 7.3
Layout group contents were only partially loading when encountering a tab overflow in nested layout groups with defer loads. This was caused by an incorrect Layout Group height calculation, and has been fixed.
SR-B30416 · Issue 292621
Removed extraneous showerrors check from onfocusinlistener
Resolved in Pega Version 7.3
After configuring a Grid item with validation rules, adding multiple records to the grid and clicking on submit without providing the values on the required fields as expected resulted in all of the error messages based on the configuration showing. An unneeded check to showerrors as part of the onfocusinlistener function has been removed to resolve this.
SR-B30438 · Issue 292802
Audit window close button function change
Resolved in Pega Version 7.3
If an Audit--View history action was configured on the KYCWorkActionsPerform navigation rule, the link worked as expected from the case manager portal but generated an error if 'audit from other actions' was used and closed before accessing the link. This was due to the close button invoking the doclose function that clears the pyworkpage. To resolve this, the Advanced/history attachments tab close button will instead invoke self.close() .
SR-B30822 · Issue 289826
SignatureDate populated correctly
Resolved in Pega Version 7.3
The out-of-the-box signature control was passing the current date to the signature date field rather than the date parameter given. This has been fixed.
SR-B31210 · Issue 290303
Draft mode defaults to off for SaveAs in Screen flows
Resolved in Pega Version 7.3
After upgrade, the behavior of Save as for Screen flows changed from defaulting from draft mode being off to draft mode being on. This was a missed use case, and has been fixed with a check in the Validate Rule-Obj-Flow activity that will not set defaultOn to true if the operation is SaveAs.
SR-B31303 · Issue 288518
Revision management GET logic revised
Resolved in Pega Version 7.3
When the revision manager creates a new revision, the second step is to add rules (strategies/data transforms etc.) into that revision so that a strategy designer can work on that. However, it was found that if one of the HTTP requests was of GET method, selecting the rules and hitting 'submit' constructed an oversized URL which listed all the rules listed on the Revision page and the browser would hang due to the GET exceeding the character limit. To avoid this, the logic used to create the post body has been modified to creating avoid long parameter values.
SR-B31533 · Issue 290736
Fixed wide repeat grid focus jump in IE
Resolved in Pega Version 7.3
When clicking on a wide grid in Microsoft Internet Explorer 11, the focus jumped to the left automatically even when all click/focus events have been removed from the grid. This has been resolved with a check so the system will not capture focus in cases where a horizontal scroll bar is present.
SR-B31665 · Issue 291063
TaskMethodHeader RUF updated to pass the param page
Resolved in Pega Version 7.3
The activity method History-Add was not adding pyTaskName in Flow FUA. This was caused by a difference in handling: Status Update via an Assignment uses the UpdateStatus activity by passing a new parameter page with only the target status value to be updated. Status Update via a Utility uses the same UpdateStatus activity by passing a parameter page created using the "CreateNewParamsPage" private method with all the required information. In order to ensure all of the needed information is available, the TaskMethodHeader RUF has now been updated to pass the param page by calling the "CreateNewParamsPage" private method.
SR-B31667 · Issue 291704
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-B31748 · Issue 291859
Stage SLA urgency correctly updates
Resolved in Pega Version 7.3
Stage SLA was updating the wrong urgency property due to the urgency value being added twice. The ExecuteSLA activity has been modified to make sure that urgency value for stage and step are updated correctly.