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.

INC-142930 · Issue 600770

Email history will be stripped from case replies

Resolved in Pega Version 8.4.4

When sending an email reply to a case, the entire email history (all previous emails in the email chain) was attached to the case as part of the reply.To resolve this, updates have been made so the system will strip history only when it's a follow-up mail. In addition, an issue with duplicate attachments has been corrected, and attachments from trailing mail will not be copied to a new post.

INC-143320 · Issue 602282

Support added for email addresses with hyphen in domain name

Resolved in Pega Version 8.4.4

When attempting to enter a email with a hyphen '-' in the domain part of an email ID (test_ab@test-email.com), the reply button was getting disabled. This was caused by the regex validation implemented in the "pzValidateEmailAddress" (Work-Channel-Triage-Email) standard activity not covering all the possible cases. To resolve this, regex has been changed to instead use a platform-provided rule to ValidateEmailAddress.

INC-145425 · Issue 600774

New email template added to include full message history

Resolved in Pega Version 8.4.4

Whenever a reply was sent from the email triage case, the outbound email sent only the actual reply along with the original email and latest reply only, skipping all remaining replies from email. For example, if there were 5 replies from case, replying 5th time generated an outbound email that contained only 5th reply (actual / current), original reply (which created the service case) and the latest reply (reply 4 in this case) and skipped reply 1 and reply 2. To resolve this, a new Outlook-style template has been added for use in replies that will include all of the previous exchanges.

INC-146544 · Issue 604495

Updated handling for unexpected character set in non-UTF-8 email

Resolved in Pega Version 8.4.4

After upgrade, the listener properly created a case from an email, but the space character was being replaced by ? in the inbound emails. Investigation showed the messages did not appear properly in the UI if the email was sent using any encoding other than Unicode (UTF-8) and it had a special character set. To resolve this, the system will remove the attachment type which includes the charset.

INC-149667 · Issue 610053

Email Triage properly maps attachments to case

Resolved in Pega Version 8.4.4

Attachments from emails coming in via the Email channel were not being attached as expected to both the Email Triage case and the case generated from that. Instead, attachments were only being added to the triage case. This was traced to the pyAttachments property not being properly updated for attachment to the generated case, and has been resolved.

INC-150367 · Issue 606030

Double quotes escaped in entity mapping

Resolved in Pega Version 8.4.4

A usecase where the BOTS created the triage cases from the emails and pushed it to the Workgroup had an intermittent problem where the screen would freeze and no actions could be performed. perform any action on the same. Investigation showed this occurred when the entity text contained double quotes which is caused JSON to break on the client side. This generated an exception during rendering, and other onload scripts failed on load and blocked the entire thread. To resolve this, the system will now avoid the JSON break by escaping double quotes in entity mapping.

INC-132590 · Issue 590491

Exported Excel from Decision Table wraps correctly

Resolved in Pega Version 8.4.4

After upgrade, entries were displayed in a single line on exporting a decision table to Excel despite WrapText cell formatting being set. This was traced to the WrapText cell formatting set under the UpdateGridCells() function being overridden inside an addDataFormat() function callas part of DecisionTableWorkBookConverter.java. This has been resolved by adding the new function "setWorkAreaCellStyles" and calling it after generateWorkbook() function call of super class (AbstractWorkBookConverter.java).

INC-140789 · Issue 597799

Added handling for validation after inactivity

Resolved in Pega Version 8.4.4

A Validate rule was configured to add an error to a field if MyPageList had any page where MyProperty was not empty. The rule worked correctly if there was no pause in using the UI, but if the UI was left for a few minutes and then the field was changed, the Validate rule always evaluated the expression to true. This has been resolved by adding a null check in Utilities.countInPageList() function.

INC-141895 · Issue 601985

Options not cached by default for picker controls

Resolved in Pega Version 8.4.4

Properties created in the data model of the case type were not showing in the drop down of custom conditions in a decision step. The property did not appear on the left hand side 'when' rule of the case designer in App Studio or Dev Studio, but did appear on the right hand side of the same 'when' rule. The issue temporarily resolved when the context class parameter was hardcoded with the class name. This was traced to the properties being cached by pzInnerEmbedConditions, and has been resolved by unchecking "Enable caching of options" for any picker control.

INC-142223 · Issue 598648

Handling added for new case type using reuse case life cycle

Resolved in Pega Version 8.4.4

Creating a new Case Type in a branch ruleset using the 'Reuse case life cycle' option was not working, and the error "branch rulseset not a candidate" was generated. pxCreateCaseDataPages that are called as part of creating a case rely on Param.RuleSetName; generally this parameter is set in the param page when other assets are created. When Reuse case life cycle was selected, other assets were not created and param.RuleSetname was not set. This affected pxCreateCaseDataPages when branch parameter was provided. This was a missed use case, and has been resolved by setting param.RuleSetName from param.ruleset to fix the issue.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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