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.

INC-192464 · Issue 681858

PackageComponent updated for use with repositories

Resolved in Pega Version 8.5.6

Exporting a zip file created by the Component wizard to a repository resulted in an error, however the same process worked as expected when the zip file was created by the Product wizard. Investigation showed that pxPackageComponent was not kept up to date with new metadata requirements for Artifactory export. This has been resolved by modifying pxPackageComponent step 7 to set Param.ArtifactType to "component" and Param.ArtifactName to [component name]_[component version]. A privilege check has also been added to zipMoveExport.

SR-B56835 · Issue 312521

Checked in SLA values updated by delegated use

Resolved in Pega Version 7.3.1

Once checked in to the application, the SLA value was not being properly updated when edited by an delegated operator and instead retained the value given by the Case Manager. This was a clipboard handling issue, and has been fixed.

SR-B65837 · Issue 317187

Handling added for blanks when copying parameter pages

Resolved in Pega Version 7.3.1

After Configuring a Call-Asynch-Activity method step on an activity and refreshing the ruleform, the name of the activity being called in the method was no longer shown. To correct this, a 'when' condition has been added to the pzAddAdditionalMethodParameter activity to handle blank pages when copying parameter pages to pyStepsParamUI pages.

SR-B67171 · Issue 317155

Handling added for blanks when copying parameter pages

Resolved in Pega Version 7.3.1

After Configuring a Call-Asynch-Activity method step on an activity and refreshing the ruleform, the name of the activity being called in the method was no longer shown. To correct this, a 'when' condition has been added to the pzAddAdditionalMethodParameter activity to handle blank pages when copying parameter pages to pyStepsParamUI pages.

SR-B65652 · Issue 315008

Corrected datasource used to update pr_extract_time

Resolved in Pega Version 7.3.1

If the "use last updated time as start" filter was used for a class which mapped to a table in an external database, a database permission error was thrown when trying to access the pr_log table in the PegaRULES database. This has been corrected by updating pr_extract_time using the connection from Pega-Extract-Time instead of the extract class.

SR-B51112 · Issue 307512

Silverlight MSI file rebuilt without registry keys for bulk installation use

Resolved in Pega Version 7.3.1

MS Word Compatibility for 2016 Office 365 was generating messages like "Error in updating the Registry Key of (AllowLaunchOfElevatedTrustApps): Object reference not set to an instance of an object." This was due to a newly-added registry keys inclusion feature on Silverlight prerequisites that not supported for installing multiple systems. To address this, the Silverlight prerequisites MSI file has been re-built without the inclusion of registry keys

SR-B69935 · Issue 317991

Pega fetch assignments API updated to call py functions for Robot Manager use

Resolved in Pega Version 7.3.1

The Pega API assignment activity pzGetAssignmentDetailsInternal in ruleset Pega-API:07-10-31 makes a call on line 16 to pzNotifyRobotWorkBasketContainer. This is a platform defect that should have been replaced with pyNotifyRobotWorkBasketContainer. pyNotifyRobotWorkBasketContainer is an extension point activity that is blank in the core platform, but overridden when the Robot Manager app layer is added to the stack. The correct py calls are now present.

SR-B68812 · Issue 317695

Activities updated to use class name to access out-of-the-box templates

Resolved in Pega Version 7.3.1

The out-of-the-box templates were not visible in the implementation layer due to the shipped templates having been created in a horizontal layer tied to a horizontal class. To correct this, the pzGetAllMappedFieldsFromTemplate and pzSetInitialSourceInfo activities have been updated to allow for loading mapping data by getting a selected template class name before calling the load template data page.

SR-B68812 · Issue 310862

Activities updated to use class name to access out-of-the-box templates

Resolved in Pega Version 7.3.1

The out-of-the-box templates were not visible in the implementation layer due to the shipped templates having been created in a horizontal layer tied to a horizontal class. To correct this, the pzGetAllMappedFieldsFromTemplate and pzSetInitialSourceInfo activities have been updated to allow for loading mapping data by getting a selected template class name before calling the load template data page.

INC-200416 · Issue 699861

Updated AttachmentPreview control for Account Manager Access Group

Resolved in Pega Version 8.5.6

When using the Account Manager Access group as the default and only access group on a profile, attempting to render a PDF on the click of a link did not work as expected. The render-on-click worked as expected when logged in as the Author and the application was switched to Account Manager. This has been resolved by registering the activity pzAppStorageOkToAttachFile in the pzAttachmentPreview control.

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