SR-131611 · Issue 201761
Currency field 'save draft' function updated
Resolved in Pega Version 7.1.8
Save Draft button when pressed caused a screen error for currency fields, identifying that they were not the proper "decimal value", though the actual flow worked as expected. This was caused by the Save Draft function passing the value in string format instead of decimal, and the API has bene updated to update the value to a number.
SR-131613 · Issue 199443
Focus set on RTE after reload section with Microsoft Internet Explorer
Resolved in Pega Version 7.1.8
On GCS Support Portal using the Microsoft Internet Explorer browser, switching the Note Type to Internal set the focus on textarea, but switching the same to External did not set the focus on RichTextEditor (RTE). The setItemFocus API has been updated to correct this.
SR-131625 · Issue 200677
Added option for validating read-only fields
Resolved in Pega Version 7.1.8
Validation was occurring on read-only fields, causing unexpected behavior. This is now a configurable option to display error messages on read-only fields that is available at the control level and cell property panels, with a default of 'false'.
SR-131648 · Issue 201958
Resolved element focus issue for Microsoft Internet Explorer with required field
Resolved in Pega Version 7.1.8
When using the Microsoft Internet Explorer browser, tabbing or clicking to the next field after the previous field is designated as Display value using read only formatting generated an error message that the field cannot be blank. An internal blur was getting fired on refocusing an element in Microsoft Internet Explorer, and a check has been added to the pzpega_ui_events.js file.
SR-131814 · Issue 200274
Cross-activity copy/paste added for steps
Resolved in Pega Version 7.1.8
An enhancement has been added to support copy/paste of activity steps across different activities.
SR-131816 · Issue 200787
Required date properties now working correctly in modal windows
Resolved in Pega Version 7.1.8
Marking a date property as required in a modal window was not actually setting the property as required. The problem was traced to a missing comma between 'date' and 'required' in the validationtype attribute on the field when there is an edit input associated. This datetime issue has been corrected.
SR-131929 · Issue 200525
Added ability to extend CDM logic with custom shapes
Resolved in Pega Version 7.1.8
In order to support adding customized shapes to strategy rules in the CDM layer, the extension point has been opened by enabling some configurations, mainly for canvas extension and shape validation.
SR-132002 · Issue 201652
Resolved date format changing with Microsoft Internet Explorer refresh
Resolved in Pega Version 7.1.8
When using the Microsoft Internet Explorer browser, the date format DD-MMM-YYYY was losing its format after refreshing or applying a validation rule or Data Constrain rule. The GenerateDatePicker logic has been updated for Microsoft Internet Explorer to correct this.
SR-132106 · Issue 200970
Decimal separator issues addressed for Microsoft Internet Explorer 9 and German locale
Resolved in Pega Version 7.1.8
Using the Microsoft Internet Explorer 9 browser and the German locale setting, the comma decimal separator was lost following several refreshes and the value was multiplied by the unanchored digits. In case of format type is "number" and "Display value using read-only formatting" enabled, the input type is generated as text but data-value was still being set with a clipboard value instead of localized value. This generation has been changed to a formatted value as data-value attribute on the input element to fix the issue. Please note that this will address customer configuration where "Display value using read-only formatting" is enabled. If this option is not enabled, the input will continue to be generated as a number and in such cases refreshes with separators may not work and can't be fixed due to browser limitation/behavior for input type number.
SR-132123 · Issue 202411
Auto-resize parameters added to Pega Image Viewer
Resolved in Pega Version 7.1.8
When a large TIFF image (over 2,000 x2,000 pixels in size) was loaded into the Pega Image Viewer control embedded into any section, both horizontal and vertical scroll bars appeared and the Fit-To-Width button of the control needed to be clicked to scale down the image enough to eliminate the scroll bars. In order to smooth image display, the system now provides image size initialization during startup using a parameter 'ImageSize' in the HTML which accepts three strings: Normal, BestFit, or FitWidth.