SR-A13882 · Issue 228926
Date Control in expandable repeating grid shows proper date value
Resolved in Pega Version 7.2.1
The Date control in the repeating grid was showing the case ID number instead of the date value when configured as master-details with expandable rows. This was due to a missed use case of the "display read-only formatting" feature where a read-only condition configured on the control returned the editable control in the response instead of read-only. This has been fixed.
SR-A13926 · Issue 230498
Resolved invalid page causing missing bulk items
Resolved in Pega Version 7.2.1
When trying to perform bulk transfer, some of the work objects were sporadically not displayed in the bulk processing list. This was caused by an invalid page getting passed while invoking checkActionWhens to act on the 'when' for showing the assignments list. The proper page is now set by updating the GETBULKPROCESSCONTENT activity to set pxRefObjectKey to the assignment page while invoking checkActionWhens.
SR-A13930 · Issue 227345
Calendar popup positioning fixed
Resolved in Pega Version 7.2.1
The calendar popover is positioned to the parent span instead of input, creating space between the input and calendar when there are errors. This has been fixed by positioning the calendar popover to the input field instead of parent span specifically for Text Input + Calendar mode.
SR-A13931 · Issue 227032
validation errors shown with datetime control
Resolved in Pega Version 7.2.1
If a server error occurred, client validation errors were not shown when the next focusable element was in datetime control. The issue here was that the Control change event was not properly bound to the calendar control in case of immediate focus, and this has been corrected.
SR-A14004 · Issue 231765
Flow designer XML fixed when using copy/paste
Resolved in Pega Version 7.2.1
Copy and paste are available in the Flow Designer, but tickets where the End shape was copy/pasted and a new ticket set created for the new End shape resulted in incorrect XML. To correct this, the flowmethodbody function will use pyTicketShapes instead of pyModifierRefs for java generation.
SR-A14014 · Issue 227004
HTTP Connector API will dynamically set TLS protocol
Resolved in Pega Version 7.2.1
The HTTP Connector was failing to connect using TLS v1.2 protocol due to the SSL Protocol being hardcoded to TLS while setting SSLContext. To fix this, the system will not pass the protocol while instantiating SSLContext, but will leave it to the API to set to highest protocol from JRE.
SR-A14106 · Issue 227981
Improved sender handling for custom email activities
Resolved in Pega Version 7.2.1
A custom email related activity was producing an authentication exception due to an attempted call to a User ID stored in Param.FromUsername made after that parameter was cleared by SendEmailNotification. To avoid this, if Param.FromUsername is blank, it will be set to the value of Param.AccountID.
SR-A14108 · Issue 242466
Better handling for rules considered duplicates
Resolved in Pega Version 7.2.1
A legacy API was not properly resolving rules present in an earlier ruleset version, leading to the creation of additional rules. The system will now consider rules already present in the earlier ruleset version and present the Other duplicate screen asking to skip, overwrite, or rename the rule.
SR-A14132 · Issue 232550
Improved handling for values starting with "." in Developer Portal Explorer
Resolved in Pega Version 7.2.1
A value starting with "." was being treated as a property and causing an exception error when using the Recent Explorer in the Developer portal. A catch has been added to resolve this issue.
SR-A14132 · Issue 233457
Improved handling for values starting with "." in Developer Portal Explorer
Resolved in Pega Version 7.2.1
A value starting with "." was being treated as a property and causing an exception error when using the Recent Explorer in the Developer portal. A catch has been added to resolve this issue.