SR-D5388 · Issue 457347
Corrected dropdown focus issue with dynamic layouts
Resolved in Pega Version 8.2.2
The focus was not retained on the dropdown field whose property was used in the dynamic layout for the refresh condition. Investigation showed that in pzpega_ui_doc_focus.js, the function "focusNextElement" was setting pega.u.d.gFocusElement set to null after the first load. This has been corrected.
SR-D39302 · Issue 507981
Report name in tab uses localization
Resolved in Pega Version 8.2.4
After creating a field value with field name as pyCaption to localize the report definition name, the title in the report definition tab was not translated. This was traced to Step 1 of the activity displayReport using an old localization function, and has been resolved by changing the localization of document title to use pyCaption.
SR-D47685 · Issue 514646
Cookie logging restored
Resolved in Pega Version 8.2.5
As part of security updates, Cookies were restricted from being logged. However, this caused some business use cases such as a custom function call to obtain the list of cookies that are present in the application to stop working. To resolve this, the cookie logging restriction has been reverted.
SR-D39302 · Issue 507980
Report name in tab uses localization
Resolved in Pega Version 8.3.1
After creating a field value with field name as pyCaption to localize the report definition name, the title in the report definition tab was not translated. This was traced to Step 1 of the activity displayReport using an old localization function, and has been resolved by changing the localization of document title to use pyCaption.
SR-D47685 · Issue 514645
Cookie logging restored
Resolved in Pega Version 8.3.2
As part of security updates, Cookies were restricted from being logged. However, this caused some business use cases such as a custom function call to obtain the list of cookies that are present in the application to stop working. To resolve this, the cookie logging restriction has been reverted.
INC-181401 · Issue 665934
Added handling for MS SQL datestamp format
Resolved in Pega Version 8.5.5
When using an Microsoft SQL Server, the browse operation was failing with an SQL error for the pyIHSummary dataset. Investigation showed there were some datasets that generated SQL statements with a date timestamp format that SQL was not able to handle implicitly, affecting browsing but not functionality. This has been resolved.
INC-181401 · Issue 665935
Added handling for MS SQL datestamp format
Resolved in Pega Version 8.6.2
When using an Microsoft SQL Server, the browse operation was failing with an SQL error for the pyIHSummary dataset. Investigation showed there were some datasets that generated SQL statements with a date timestamp format that SQL was not able to handle implicitly, affecting browsing but not functionality. This has been resolved.
INC-181401 · Issue 665936
Added handling for MS SQL datestamp format
Resolved in Pega Version 8.7
When using an Microsoft SQL Server, the browse operation was failing with an SQL error for the pyIHSummary dataset. Investigation showed there were some datasets that generated SQL statements with a date timestamp format that SQL was not able to handle implicitly, affecting browsing but not functionality. This has been resolved.
SR-127306 · Issue 193879
Added special character handling for Tooltips labels and icons
Resolved in Pega Version 7.1.8
Tooltips on labels and error icon were displaying the corresponding escape characters instead of the special characters intended. HTML screens did display these characters correctly. There was a workaround overriding the function in UserWorkForm, but this has been resolved by ensuring the value is html encoded and tooltip is using this value.
SR-A2721 · Issue 206236
Fixed logging directories for PegaRULES
Resolved in Pega Version 7.1.9
After upgrading to a split schema, PegaRULES and PegaRULES-ALERT were written to a single file in the home directory despite the prlogging.xml file specifying the file name and path. This was due to a missing prlogging.xml function in the prresources-non-config.jar, and has been fixed.