SR-A77023 · Issue 257680
Fixed Firefox Checkbox onclick events triggering when not clicked
Resolved in Pega Version 7.2.2
When using Firefox, clicking in between the label and checkbox captured the target as span. Data-click actions were configured to trigger with this click, but the logic to toggle the checkbox value on click was missing. This has been corrected in ui_events on clickHandler.
SR-A77023 · Issue 255255
Fixed Firefox Checkbox onclick events triggering when not clicked
Resolved in Pega Version 7.2.2
When using Firefox, clicking in between the label and checkbox captured the target as span. Data-click actions were configured to trigger with this click, but the logic to toggle the checkbox value on click was missing. This has been corrected in ui_events on clickHandler.
SR-A94142 · Issue 263214
Check added to handle submitModal button use
Resolved in Pega Version 7.2.2
After upgrade, running a script under the actions tab of a button was not working as expected though the standalone run did work. This has been fixed with the addition of a check to differentiate between a pzModalButton and a normal button.
SR-A99523 · Issue 266451
LockInformation section uses field value label
Resolved in Pega Version 7.2.2
The label in pzLockInformation section was hard coded, causing the string "You have lost the lock! Please reopen the item to continue your work." to not have a field value. This has been changed to create a Field Value and use the same in the label.
INC-177323 · Issue 672420
Search string wildcard use documentation updated
Resolved in Pega Version 8.7
The support article for the search API has been updated to clarify the ability to use the wildcard character "*" by manually adding it to the prefix of each term in the search string.
INC-173162 · Issue 650795
Certificate match will use Subject Distinguished Name
Resolved in Pega Version 8.7
Signature verification was failing due to the system not finding the matching root certificate for the chain. The root certificate was in the trust store, but the system found a different certificate first and that other certificate (an intermediate certificate) was not considered a valid certificate for validating the whole certificate chain. This was traced to filtering on the Issuer Distinguished Name (DN) instead of the Subject DN and was due to intermediate certificates potentially having the same Issuer as a root certificate (e.g. if that root certificate was used to create the intermediate certificate). To resolve this, an update has been made to check the Subject DN instead of Issuer DN.
INC-189047 · Issue 674759
Session timeout adjusted for use with Apple Safari
Resolved in Pega Version 8.7
A configured browser session logout timer was not working with the Apple Safari browser. This was traced to browser-specific handling for self.location.href and has been resolved by adjusting the logic and moving it inside a setTimeout to improve cross-browser compatibility.
SR-A85709 · Issue 255759
Cleared erroneous dirtycheck popup on DropDown using lazyload
Resolved in Pega Version 7.2.2
When a pxDropDown was configured with load mode "After screen renders", the "selected" attribute was not correctly set on the HTML and the dirtyCheck failed even when the values were saved. This was due to the "Selected" attribute on options tag not being set properly when the dropdown mode was set to lazyload (after screen render), and has been fixed.
INC-189259 · Issue 674820
Big Decimal used while converting List to Page
Resolved in Pega Version 8.7
Previous work done to handle precision numbers in the JSON response that were being rounded or truncated when parsed for the DataSource page has been updated to also handle the case of mapping a list to a page.
SR-A88481 · Issue 256518
VBS starts with DDS configured to use external Cassandra
Resolved in Pega Version 7.2.2
If DDS is configured with Internal Cassandra which is then switched to External, DDS reports to be in state NORMAL and VBD can start. However, when starting from scratch with DDS configured to use External Cassandra, DDS was failing validation and reporting to be in state CLIENT, so VBD was unable to start due to VBD's check that ensures at least one DDS is in the NORMAL state before starting. To address this, the validation code that checks the DDS state when VBD is starting has been removed and the system will instead rely on the DSM service layer to ensure that DDS is functional before VBD can start.