SR-132675 · Issue 201772
Removed quotes from dropdown placeholder FV
Resolved in Pega Version 7.1.9
Place holder text in a dropdown was being changed to a string and displaying with quotes even though a field value was selected. This has been resolved by adding logic to not add quotes when a valid field value is entered, and to handle single-escaped quotations.
SR-132720 · Issue 203636
Resolved stale transaction error on editing operator skills
Resolved in Pega Version 7.1.9
After creating a control that displayed a listview of operators in a side panel with a single click event on the list view to show a button, clicking the button was intended to open an out-of-the-box html rule "ShowSkills" which is used to show/update the skills of the operator. However, on the "ShowSkills" screen the error "This action is not allowed as it is outside the current transaction" was being generated when trying to update the operator skills. This was caused by a stale transaction error, and has been resolved by adding the type 'button' on the buttons in the ShowSkills HTML code.
SR-132804 · Issue 202829
Error messages displayed for read-only checkboxes
Resolved in Pega Version 7.1.9
When a validation rule was configured on a checkbox such that if it does not contain a true value it should display error message beside this checkbox when user clicks on submit button, the message was being displayed properly in edit mode but at runtime this error message was not displaying if set to 'read only'. This has been resolved by adding the correct error message generation for read-only configurations.
SR-132927 · Issue 206255
Information on iPad Safari focus issues
Resolved in Pega Version 7.1.9
An issue was found where the onScreen Keyboard disappeared on refresh of a focused input element when using Safari on an iPad. Unfortunately, iPad Safari has compatibility issues with programmatic focusing and this problem cannot be resolved in the PRPC software. The root cause is the browser security: even though focus is getting triggered (value can be set , focused element is the document.activeElement) on the targeted input element, focus behavior (like blue border highlighting, keyboard popping up) is not triggered when the focus in call stack comes from within a function and the first function in the call stack was triggered by a non-programmatic event. Instead, the security mechanism kicks in to prevent you from setting focus on the input. As this is not a PRPC issue, we cannot offer a resolution at this time.
SR-133040 · Issue 203518
Removed duplicate special character encoding on FieldValue validation
Resolved in Pega Version 7.1.9
A recent change was made to the "Validate" activity of the Rule-Obj-FieldValue class to improve security by performing a filterRichText (intended to remove unsafe tags like script tag). However, this broke a reported use case where field values used as the source for the controls dropdown, checkbox, or radio buttons displayed the encoded values of quotes due to double encoding. To fix this, the filterRichText step has been removed from Rule-Obj-FieldValue!validate activity.
SR-133040 · Issue 202460
Removed duplicate special character encoding on FieldValue validation
Resolved in Pega Version 7.1.9
A recent change was made to the "Validate" activity of the Rule-Obj-FieldValue class to improve security by performing a filterRichText (intended to remove unsafe tags like script tag). However, this broke a reported use case where field values used as the source for the controls dropdown, checkbox, or radio buttons displayed the encoded values of quotes due to double encoding. To fix this, the filterRichText step has been removed from Rule-Obj-FieldValue!validate activity.
SR-133241 · Issue 203013
Enabled NotFutureDate date for Thai Locale
Resolved in Pega Version 7.1.9
The validation notfuturedate was failing with the current date when using the Thai locale. The getDateFromFormat function has been updated to properly localize.
SR-133352 · Issue 206143
Calling Page-Set-Messages via activity now properly displays errors
Resolved in Pega Version 7.1.9
After upgrade, calling Page-Set-Messages via an activity did not appear to set messages on the harness. Changing the id ErrorTable to ErrorTable1 in the Errors section displayed the messages, but without any formatting or expand/collapse section. The error messages were indeed being set properly, but were being reset due to a rollback request to pzUpdateElementModel. To resolve this, pzKeepPageMessages is now being sent as true for rollBackElementUpdate request in pzpega_ui_doc_lifecycle.js to retain the errors displayed after the request.
SR-133352 · Issue 206222
Calling Page-Set-Messages via activity now properly displays errors
Resolved in Pega Version 7.1.9
After upgrade, calling Page-Set-Messages via an activity did not appear to set messages on the harness. Changing the id ErrorTable to ErrorTable1 in the Errors section displayed the messages, but without any formatting or expand/collapse section. The error messages were indeed being set properly, but were being reset due to a rollback request to pzUpdateElementModel. To resolve this, pzKeepPageMessages is now being sent as true for rollBackElementUpdate request in pzpega_ui_doc_lifecycle.js to retain the errors displayed after the request.
SR-133388 · Issue 203251
Fixed space overrun display issues for localized text in Designer Studio
Resolved in Pega Version 7.1.9
If the localized non-English text length was lengthy, it was overrunning its space and crossing into adjacent sections of the Explorer tab of Designer Studio. This has been corrected by adding style code to handle the left and right orientation of tabs, which is especially critical for Japanese and Arabian characters.