INC-136768 · Issue 588452
Question Wizard import will downcase answer types to match system requirements
Resolved in Pega Version 8.3.5
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-148099 · Issue 607290
Resolved button flicker
Resolved in Pega Version 8.3.5
The buttons were flickering when moving between screens in an offline-enabled mobile app. This has been corrected.
INC-146521 · Issue 602657
Survey Question Page Radio/Dropdown Button retains value
Resolved in Pega Version 8.3.5
After creating an Interaction from the portal and selecting "Survey", the Survey Question Page using a Radio button/Dropdown button as Question did not retain the value after a selection was made. This has been resolved by modifying the refreshSurvey method in pzsurvey_ui_userscript.js to work with an Ajax container.
INC-144311 · Issue 601109
Updates for nested "Append And Map To"
Resolved in Pega Version 8.3.5
Nested actions "Append And Map To" in Data Transforms were producing incorrect results when offline. This was traced to all operations being performed on the Page List which was on first level of nesting, which was caused by changing the Data Transform into JavaScript form for offline use. The JavaScript form of DataTransform uses variable the "targetListObj" to represent the Page List, and this same name was reused regardless of the "Append And Map To" nesting. An additional problem was seen with the "Update Page" Data Transform action when used with conjunction with a nested "Append And Map To" action: the action assumes that top level Pages exists, but "Update Page" did not create them. This caused the "Append And Map To" action to fail. To resolve this, the "Append And Map To" action will use suffixed variable names to reference nested PageLists, and "Update Page" will create the Page if it doesn't exist.
INC-144566 · Issue 600857
User lookup list correctly populated when using # tag
Resolved in Pega Version 8.3.5
When typing '#ANewTag @' in Pulse, the user lookup list was not shown. Using '#ExistingTag @' worked as expected. This was a missed use case in work done to improve the performance of pzJquerymentionsInput by restricting REST calls, and has been resolved.
INC-139861 · Issue 594006
Cross-site scripting protections added to Case Email
Resolved in Pega Version 8.5.4
Cross-site scripting updates have been added to rules handling linked email correspondence.
INC-147873 · Issue 610865
Custom header character encoding for Subject added
Resolved in Pega Version 8.5.5
Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers.
INC-145802 · Issue 636324
Oracle temporary space explicitly freed after writing LOBs
Resolved in Pega Version 8.5.4
Oracle temporary space used to write the LOB was not freed up after writing records to Log-Service-File when using OJDBC8 or OJDBC10 versions and the table involved had inline BLOB storage such as small blob tables like Log-service-file (2-4kB blobs). This did not occur when using OJDBC7, but investigation with Oracle could not determine why the older version did not have this issue. This issue has been resolved by explicitly freeing the LOB space with a call to free() / freeTemporary() , a utility for LOB objects that was introduced in JDBC 4.
INC-154026 · Issue 631041
Resolved exception from expanding deserialized Data Page
Resolved in Pega Version 8.5.4
When using a data page backed by a report definition where the data page data type was Rule- and the virtual page data type was Rule-Obj-Property, serializing and deserializing the data page and then expanding the deserialized data page generated the exception "the reference .pzInsKey is not valid. Reason: .pzInsKey is mapped to class Rule-Obj-Property, which is not the primary class of the list: Rule-; must specify a group name in mapping". The issue occurred only if "Run on Data Page" on the data page was checked and "Report on descendant class instances" on the report definition was unchecked, and has been resolved by updating the runLoadActivity() of DeclarativePageDirectoryImpl to skip setting pyObjClass for the report definition if it already present, i.e. if already set by the loader activity.
INC-155624 · Issue 634716
MSGraph email listener enhancements
Resolved in Pega Version 8.5.4
Attachments with .eml /.msg extensions were treated as FileAttachments by the MS Graph API and generating a classcastexception. To resolve this, a check has been added to identify the attachment along with content type so .eml will be correctly recognized. In addition, the MSGraph email listener functionality related to converting from Graph to MIME message has been enhanced around the 'TO' and 'CC' recipients in a MIME message and for parsing nested attachments in Item attachment for addition to MsgraphMessage.