SR-119560 · Issue 175797
Updated ObjCass name handling for XML generation
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When an extract rule is run with output as XML and the pxObjClass was not selected manually, the XML generated had pxObjClass tag and values, but the definition was not present in XSD. This was caused by the code that generated the XML having pxObjClass set in the resulting page; this was incorrect as pxObjClass needs to be written to XML only when it's selected or if the -c option is used to differentiate different classes in the hierarchy. The code has been updated.
SR-119578 · Issue 175170
PDF field mapping corrected for modal dialogs with Internet Explorer
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When using Internet Explorer , some fields within a modal dialog were not properly populated in a generated PDF. This was caused by the PlaceHolder text becoming an actual value after an AttachAfile local action with a multi-part content file, and has been resolved.
SR-119610 · Issue 177443
Corrected resizing issue with screen layout skin
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
An issue was found when mixing re-sizable and non-re-sizable widths in the Header 'Left Right Screen' layout for EndUser71 skin. On screen load, the panels appeared with the correct size, but once the right panel was closed and reopened, it reopened to the size given for the 'Left Panel Width'. This has been corrected.
SR-119683 · Issue 177507
Enhanced integer rounding options available in repeating grids
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
While the engine supports all integer rounding options, those options were not fully available in repeat grids where one row has the pxInteger control. An enhancement has been added to support all available rounding options in this control.
SR-119725 · Issue 176399
Smoothed Report Definition handling for missing or incorrect ObjClass
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
In some situations, a Null Pointer Exception was being generated after a call to a report definition on the Report Content Page. This occurred when given a target results page with a missing or incorrect pxObjClass. The code has been modified to generate the error "Invalid Report Content Page" instead of the NPE if the ObjClass is incorrect, or to complete the processing if the ObjClass is empty.
SR-119858 · Issue 175151
Adjusted code to prevent double-localization when using Google Chrome
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When utilizing a locale that uses commas instead of points to demarcate decimals in numbers, editing any numbers in a skin caused extra zeros to be added to the numbers. When using Google Chrome, if an input type is a number, Google Chrome by default will localize. The control is also localizing the value after reload, so localization is happening twice. In order to resolve this, If the input type is text, only control localization will happen.
SR-119869 · Issue 176176
Access Role Editor link errors fixed
Resolved in Pega Version 7.1.7
When using IE11 or Google Chrome, clicking on the hyperlink to a privilege associated with a class in Access Role Editor created issues that prevented changes from being made or saved. In some cases, after clicking 'Remove Checked' in the popup dialog, the developer portal loaded in the popup. This was caused by the forms-based role selection not being converted for cross-browser support, and has been fixed.
SR-119909 · Issue 176760
Fixed page toggle when a grid contains an error
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
It was not possible to navigate to a different page in a grid when a validation error existed on any page.The error could be corrected if it occurred on the current page and paging ability would return, but if the error as in a different page it was not possible to navigate to correct it. This was traced to code which prevented moving to another page if there was an error on refresh. While there was a workaround, the code has been updated to allow moving to another page unless the error occurs on the current step page.
SR-119926 · Issue 177335
Smoothed handling of dynamic select with refresh section
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
In the course of server-side prep of the list for a Dynamic Select (via a long running activity wrapped up with a per interaction refreshing Declare page), the Refresh Section event is getting fired. This causied the properties bound to Dynamic Select controls (either in read-only or editable modes) to lose their values. This was resolved by modifying the dynamic select code to load the dynamic select values and set default value upon refresh action (even in case of readonly).
SR-119989 · Issue 176616
DateTime control logic improved for repeating grids
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
If a repeat grid was configured with 'pxDateTime' control for one of the columns, clicking the 'calendar' icon for the first time would not show the calendar. Thereafter, the calendar would appear on icon click. This was found to be an error in the javascript logic where the DatePicker function was returning false even if the event was from the DatePicker control. This has been corrected.