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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-C28090 · Issue 370297

Apache library updated

Resolved in Pega Version 8.1

To improve security, the following updates have been made: - Apache Commons FileUpload updated to version 1.3.3 - Apache-mime4j-core has been updated to version 0.8.1 - Apache POI has been upgraded to version 3.17

SR-C28092 · Issue 370330

Service Utils repackaged for Linux

Resolved in Pega Version 8.1

Running ant or prpcServiceUtils.sh on a Linux instance was failing with the error "bash: ./scripts/bin/ant: /bin/sh^M: bad interpreter: No such file or directory". The Service Utils have been repackaged to correct this issue.

SR-C28093 · Issue 368876

Apache library updated

Resolved in Pega Version 8.1

To improve security, the following updates have been made: - Apache Commons FileUpload updated to version 1.3.3 - Apache-mime4j-core has been updated to version 0.8.1 - Apache POI has been upgraded to version 3.17

SR-C28094 · Issue 369459

Apache library updated

Resolved in Pega Version 8.1

To improve security, the following updates have been made: - Apache Commons FileUpload updated to version 1.3.3 - Apache-mime4j-core has been updated to version 0.8.1 - Apache POI has been upgraded to version 3.17

SR-C28260 · Issue 369661

System will not add quotes to Data Page string parameter

Resolved in Pega Version 8.1

After creating a unit test for a Data Page that requires a string parameter, the unit test failed because the parameter value entered was placed in quotes. This requirement was not clear: Double quotes were shown in the test rule form even though the actual value was not expected to be input with quotes, and the system was adding them. To remove confusion, the system will no longer add the additional quotes so they are not doubled.

SR-C28265 · Issue 374085

Optimized properties “pyFieldClass” & “pyFieldName”

Resolved in Pega Version 8.1

The properties pyFieldname and pyFieldClass were not optimized, leading to errors if these properties were used in out-of-the-box report definitions run without UDF enabled. As part of this fix, the columns will be created in the database and need to be populated.

SR-C28389 · Issue 374701

Added check for parent page when using 'save-as' in PM BundleTemplate

Resolved in Pega Version 8.1

Pega Marketing has a longstanding shipped section called BundleTemplate which is used to render a page-list of bundle members for emails. Doing a save-as of this section (without ANY changes) was resulting in runtime errors with the exception ":com.pega.pegarules.pub.clipboard.InvalidReferenceException: The reference .BundleOfferMembers(1).BundleOfferMembers is not valid. Reason: Entry handle must have a page name specified." This happened because the Section in grid was run on a page without a name, and the exception came from test id generation code which expected a complete path of the grid page list property. In this case the path is not complete as it starts with "." (dot) and there is not a top level named page. To resolve this, the code has been modified to not generate a test ID when the parent page does not exist in Clipboard.

SR-C28508 · Issue 368620

German language pack updates

Resolved in Pega Version 8.1

The German Language Pack (_de) has been updated to properly display the German text for rich text editors text like (Bold, Italic,) and the 'Check Spelling' tooltip.

SR-C28579 · Issue 384591

Delegated data types show correct tab header name

Resolved in Pega Version 8.1

When the delegated rules were opened from the case manager portal via configuration page in a multi DC portal, the tab name was shown as insname of the data type class. This was caused by the "pyInsHandle" property being configured for the name parameter for the landing page action. To correct this, the system will use "pyOriginatingLabel" instead of "pyInsHandle" in the pzDelegatedRulesGrid section to display the rule label.

SR-C28586 · Issue 377237

Error with fetching prompt value fixed

Resolved in Pega Version 8.1

When property was configured with declare expression and its read only value was given as 'Display text of selected options', it showed the standard value instead of the prompt value. This has been corrected with code changes to get the prompt value of the given configuration.

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