INC-153163 · Issue 615114
Header present in timeout modal window
Resolved in Pega Version 8.5.3
After upgrade, the header was missing in the session timeout modal dialog when using the pzDisplayModalDialog FlowAction with the pzDisplayModalDialog HTML Rule. This was traced to the title value fetched from HTML not being set for use in the onload function of iframe, and has been resolved by ensuring it is handled by the pzDisplayModalDialog HTML rule.
INC-153086 · Issue 619321
Job scheduler tracing updated for multi-node
Resolved in Pega Version 8.5.3
When attempting to trace the job scheduler using "trace any node", the error "Unable to trace trace job scheduler 'ConsumerPathRequestEvents' on node as the scheduled tracer information was reset" appeared intermittently. When Job Scheduler is configured to run on "any associated node" and the trace is designated as "trace any node" option, the implementation was running the trace on the node that received the request which may or may not be the one running the job scheduler. This was not an issue when tracing a job scheduler that was running on "all associated nodes". To ensure the correct node is found, when using "trace any node" for the job scheduler, the system will now look for the eligible node and return the requestor ID for the trace.
INC-136768 · Issue 588450
Question Wizard import will downcase answer types to match system requirements
Resolved in Pega Version 8.5.2
The Question Upload wizard would not create a File type question while using a survey template. The template has a column Answer mode in which accepts an input of the type of answer expected, but in this use case "File" was given instead of "file", resulting in the question being created using the default values. To resolve this, during the import process when the system parses the file and gets the contents from the data using the pzSetdefaultValuesforQuestions DT, mode values will be explicitly set to lowercase.
INC-150395 · Issue 625070
Tokenizer updated to handle commas
Resolved in Pega Version 8.5.3
The Text Analyzer was not working as expected in cases where the number was combined with a comma (,) with it but was working when a space was used between the number and the comma. This was traced to the tokenizer not correctly processing and splitting the input text when there was a special character before or after the token. This has been resolved by updating the tokenizer logic.
INC-148272 · Issue 609001
Increased specificity for collapsed DL
Resolved in Pega Version 8.5.3
When using the collapsible header functionality of a container skin format, the styling was not being applied correctly to the header. This has been resolved by increasing the specificity for a collapsed dynamic layer.
INC-149953 · Issue 613729
Increased specificity for collapsed DL
Resolved in Pega Version 8.5.3
When using the collapsible header functionality of a container skin format, the styling was not being applied correctly to the header. This has been resolved by increasing the specificity for a collapsed dynamic layer.
INC-184798 · Issue 703269
PRconfig added for JVM user/password
Resolved in Pega Version 8.7.1
The setting Dcom.sun.management.jmxremote.local.only=true has been added for use when JMX authentication is enabled by providing jmxuser/password through prconfig.
INC-139849 · Issue 598127
Sorting icon visible for table in Cosmos on Google Chrome
Resolved in Pega Version 8.5.2
Tables were not showing any sort icon / indicator in the column header when using the Cosmos Theme in Google Chrome. This was only occurring in apps created with the Cosmos theme, and was caused by the sort icon for a non-optimized table using display flex, resulting in the position of the icon being displaced. This was a missed use case of having a non-optimized table in Cosmos, and has been resolved by removing the non-optimized-related CSS code.
INC-146610 · Issue 610483
MimeTypeHandler added for cloud downloads on mobile
Resolved in Pega Version 8.5.3
When using the Pega cloud storage repository (Application -> Integration -> Content Storage) with the Google Chrome browser on an android device, it was possible to upload attachments but re-downloading the attachments failed. Investigation showed that this was due to the content-type appearing as application/* so Google Chrome on mobile was not able to identify the file type. This was a missed use-case for returnFileForDownload(), and has been resolved by setting the system to use MimeTypeHandler for getting the content type.
INC-148392 · Issue 610670
File type handling added for cloud downloads on mobile app
Resolved in Pega Version 8.5.3
When using the Pega cloud storage repository (Application -> Integration -> Content Storage) with the mobile app, it was possible to upload attachments but re-downloading the attachments failed. Investigation showed that this was due to the content-type appearing as application/* so the file type was not able to be identified. This was a missed use-case for returnFileForDownload(), and has been resolved.