SR-A642 · Issue 206621
Enabled section autogeneration from HTML to JSP
Resolved in Pega Version 7.1.9
Effective with Pega7, section generation was changed from HTML(pyJavaGenerateAPIVersion = 04-01) to JSP(pyJavaGenerateAPIVersion = 04-02). This caused an issue with some migrations from earlier versions that were not able to make the mandatory switch from HTML to JSP generation due to a missing option in the section ruleform. The option to upgrade from HTML to JSP had been configured from within "pyAutoHTML = false", meaning that this option appeared only for non-autogenerated sections. To resolve this, the option "Generate for" in the section Rule-HTML-Section.pzRuleFormHTML is now available irrespective of whether pyAutoHTML is set to true or false.
SR-A681 · Issue 205448
Added handling for empty section name in reload
Resolved in Pega Version 7.1.9
A Null message was sporadically displayed when hovering over a row instead displaying the SmartInfo section or a loading icon. This was caused by an empty section name in the reload section ajax, and handing for this has been added to the SmartHarness API.
SR-A833 · Issue 204781
Fixed Google Chrome 43 population of Dynamic Select and Menu control
Resolved in Pega Version 7.1.9
When using Google Chrome Version 43.0.2357.81 m, no values were shown in the Dynamic Select drop down list or in the Menu control. This was due to an uncaught exception for this browser in the JavaScript code which has now been addressed.
SR-A91 · Issue 205459
Added expand on click logic to check for layouts collapsed on open
Resolved in Pega Version 7.1.9
The ?Expand/Collapse? click event was not working on the first click if all layouts/sections were initially collapsed on open. This was due to the logic used to determine the state of the layouts, and an additional check has been inserted to handle scenarios where the layouts/sections are collapsed on-load.
INC-136091 · Issue 598907
Activity updated for Mobile attachment access
Resolved in Pega Version 8.3.5
Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type.
INC-135720 · Issue 594794
Case link shows in Social messages for the old cases
Resolved in Pega Version 8.3.5
After upgrade from v7, the case link was not visible for the cases that were created in the old platform version. In Pega 7.1.7, metadata was stored in .pyPrivacyContextor while the later versions are using .pxContextType for Case type to show the related data. To resolve this, new properties have been implemented to hold the Case ID link.
INC-139160 · Issue 590255
Case tags made available for search filtering
Resolved in Pega Version 8.3.5
An enhancement has been added for obtaining the list of cases (of a specific type) based on a tag or case type. Clicking on a tag associated to the case will filter all the cases (of that case type) with that tag, and selecting more tags will refine the filter.
INC-146114 · Issue 604413
Create Survey routes case correctly
Resolved in Pega Version 8.3.5
The Create Survey utility was not routing the case to the user who initiated the case, but instead was routing it to the user who checked-in the case. This was traced to an error related to pxRequestor.pxUserIdentifier in the data transform pzpopulate survey params which is called when the survey utility is used, and has been corrected.
INC-146676 · Issue 601942
Field Service app localizations updated
Resolved in Pega Version 8.3.5
Localization has been added to the 'getDirections' alert and other popup alerts in the Field Service app.
INC-131592 · Issue 583437
Jsoniter parser upgraded
Resolved in Pega Version 8.3.5
After upgrade, the pxTextinput property Prompt List was being converted into decimal upon clicking finish assignment. This was traced to the jsoniter parser, and has been resolved by upgrading the parser in the jsoniter library.