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-D42244 · Issue 507486

Top page reference made explicit for alternate stage visibility condition

Resolved in Pega Version 8.4

After upgrade, trying to use Save-As on the caseType rule to move it to a higher Ruleset version resulted in the alternate stage configuration setting not showing correctly. This was due to the "set Value" action not being performed correctly when the save-as was performed, causing the client visibility condition on the DL cell which included the master details section to not be shown. This has been corrected by ensuring there is a proper reference to the top page in this scenario.

SR-D43807 · Issue 512048

Localization added to File upload alerts

Resolved in Pega Version 8.4

When uploading files as part of adding attachments, error and warning messages were displayed as alerts in English despite using localization. This was traced to the pzMultiDragDropControlStandard control rule having the HTML alert messages hard coded instead of using field values which could be localized. To resolve this, field values have been created for the messages related to DragDropMaxSize, FileNotExistMessage, FileUploadSupportMessage, and UnableToLoadFileMessage.

SR-D47018 · Issue 517033

Corrected parameter being encrypted during change portal configuration

Resolved in Pega Version 8.4

After configuring a changePortalLayout control using .pyDescription as property, trying to switch the portal was throwing a error page. The same configuration worked in earlier platform versions. This was traced to recent updates where the activity parameter ended up being encrypted along with the activity name, and has been resolved by removing the parameter from encryption input and adding it to encryption output.

SR-D47146 · Issue 515649

Pick Values modal updated for deprecated list view handling

Resolved in Pega Version 8.4

Pick values were not displaying in the menus below Case Management-> Tools -> My Work, including "Work entered by me", "Work by workbasket", and "Work resolved by me recently". This was due to the use of deprecated list views: the pick values modal was failing to show and hide the busy indicator because the indicator now uses jQuery, but list view does not include jQuery. In order to resolve this, the equivalent Report Definition pyEnteredByMe has now been added under the navigation rule : pzProcessAndCaseRulesMainMenu.

SR-D47312 · Issue 513568

pxGenerateExcelFile updated for handling blank dates

Resolved in Pega Version 8.4

When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date or to 1/1/1970. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format.

SR-D51535 · Issue 519476

Enhanced discrimination for tasks in MyPega spaces

Resolved in Pega Version 8.4

When using My Pega for spaces and tasks, using drag and drop to move many cases around quickly resulted in tasks intermittently ending up in a state where they could not be updated further and became unusable. Analysis showed that because the milliseconds part of the update time was rounded, the logic of comparing for value between 0 and 1000 failed when the comparison returned -ve value. To resolve this, the comparison has been modified to !=0 and the 'when' rule pyContinueTaskProcessing has been added as an extension along with the appropriate usage guide to restrict processing. By default, the system will consider task name, description, due date, assignee, and rank properties; if more properties are needed to evaluate, this when rule can help.

SR-D54200 · Issue 516776

Custom attachment category parameter passed to dropdown

Resolved in Pega Version 8.4

Attempting to use the out-of-the-box “Attachments control” which was configured at design time to use a custom category where both the custom category and the section class were in the same work class resulted in the attachment category dropdown defaulting to “File” instead of the custom category. Investigation showed that the custom attachment category name configured on the control was missing in one of the pre-processing activities sequence. To resolve this, the activity Work-.pzInitAttachContent and the initAttachmentPage activity have been updated to pass the custom attachment category parameter.

SR-D67323 · Issue 529948

XSS filtering added for CreateMergedWordDoc

Resolved in Pega Version 8.4

XSS filtering has been added for the TemplateName parameter value in the CreateMergedWordDoc section.

SR-D17987 · Issue 494485

Check added for backwards compatibility with Case Type when rules

Resolved in Pega Version 8.4

After upgrade, the When rules present on case type rules (used for skipping stages or showing/hiding stage-wide or case-wide actions) were not executing at run time. This was traced to the introduction of the pySkipOrAllowType property in recent versions, and was only reproducible when the ApplicationRuleset was locked and after upgrade irrespective of whether the condition for when was true or false. To resolve this and enhance backwards capability, a check has been added for the SkipOrAllowType property being empty.

SR-D24750 · Issue 501748

Resolved importing PublicFormat file using RuleFromFile Wizard

Resolved in Pega Version 8.4

When attempting to create a flow from a Public Format XML file using the Rule From File Wizard, the following error was seen: "Problem invoking function: pega_procom_harvest.performXSLT--(String,String,boolean,HashStringMap)". This was caused by a mapping failure related to the pyComments property in baseclass pega social functionality, and has been resolved with the addition of a new page group property pyComments of type "Data-MO-Annotation-Comment" which applies to "Embed-Rule-Obj-Flow-ProcessModel".

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