Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

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.

SR-132135 · Issue 202410

Smoothed 'save as' for private reports without checkout privs

Resolved in Pega Version 7.1.8

When a user did not have checkout option either at the operator level or at the design time rule-set level, trying to use 'Save As' on Report definition rules reports in Private category resulted in an error but actually saved the report at the back end. Opening the Case Manager portal and trying to do a 'save as' of an existing report led to the report category being populated as private but the standard categories got populated in the drop down. If OK was clicked, then the standard categories were replaced with private category. To improve this, a check has been added to detect a non-developer operator, who is then allowed to save in their personal category.

SR-132143 · Issue 201187

Enhancement added to allow setting extract directory for BIX

Resolved in Pega Version 7.1.8

An option has been added to override the output directory of the command line BIX extraction. The command line parameter -P allows specifying the desired path by saving a copy of the Extract Rule XML and setting appropriate pyOutputDirectory path value in it.

SR-132265 · Issue 200632

Improved hotfix detection

Resolved in Pega Version 7.1.8

Migrating from ML6 to ML7 was failing with an error reporting the system contained hotfixes that were generated after the release of ML7. This was due to the ML Readiness step incorrectly identifying pre-7.1 rules as having been updated after the upgrade to 7.1.6. This happened when the revalidate and save was run after the release of ML7, which updated the pxUpdateDateTime for the rules in question and led to them being caught by the validation. This was meant to catch hotfixes, and the handling has been improved to avoid this error.

SR-132414 · Issue 201583

Resolved duplicate result column on Decision Table

Resolved in Pega Version 7.1.8

On a decision table rule, checking "Allowed to return values" check box caused an additional Result column to be added to the table configuration if the Microsoft Internet Explorer or Google Chrome browser was used. On saving, this erroneous result column was inconsistent about being removed. This has been corrected.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us