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-C68219 · Issue 406591

Customizable extension points added to Work-.CorrAttach

Resolved in Pega Version 8.2

In order to support the use of custom properties on Link-Attachment instances when correspondence is sent and attached to the case, extension points have been provided for pyDefault data transform in the activities Work-.CorrAttach.

SR-C57545 · Issue 396123

Corrected retrieval of externally-stored PDF attachment

Resolved in Pega Version 8.2

After generating a PDF using the out of the box activities GenerateEForm and AttachEForm, the message "Failed to load PDF document" was displayed with a Reload button when trying to open the attachment. This was traced to an implementation error when CMIS/WebStorage/Repositories was updated that neglected to modify AttachEForm to match extra properties that were added to AttachFile. This caused issues when storing an attachment in an external storage system that was skipped in AttachEForm. To correct this, the Link-Attach file has been modified to properly to indicate where the attachment is being stored when it is stored externally.

SR-C80753 · Issue 419246

Native calendar control works for Firefox on Android

Resolved in Pega Version 8.2

When using Firefox with 'Use native control on mobile' checked, attempting to enter a date into the DateTime field highlighted the mm field but the date selector did not open and keyboard entry was not recognized. This was traced to the native calendar for date time control not opening in Firefox on Android. To correct this, type checks for date, time and datetime-local have been added to the isTextBox function in pzpega_ui_events_infra js.

SR-C62412 · Issue 402624

VBD enhancements added to assist in cleanup

Resolved in Pega Version 8.2

Running VBD for a long period of time will lead to accumulating partition summaries without a safe means to clean up. Enhancements have now been added to support the following:1) An API has been added to VBDService to support deletion of partitions from cache AND persistence prior to a date. This can be used as a building block for "keep last X days" functionality on a VBD dataset. 2) The Start Date will be used when loading Partition summary data when the service initially loads. Eviction logic has been implemented to remove partitions along with summary data (e.g. counts and dictionaries) for partition keys earlier than Start Date. Eviction occurs when Start Date moves ahead of partition's timestamp. If Start Date is updated backward by user and there exists data in Cassandra on these dates, then the partition summaries should be loaded into the cache. This requires a full cache reload which will be automatically triggered.

SR-C62835 · Issue 408359

pzReindex defaults to true during branch merge and initial save

Resolved in Pega Version 8.2

When using Declare Indexes intended to be fired when a KYC rule type was saved, merging a KYC rule type from a branch to a ruleset which contained the rule resulted in the declare indexes not firing from Rule-pyMergeInstance. If the branch was merged into a ruleset which did not contain the KYC rule, the Rule-pyMergeInstance fired the declare index rules as expected. This was an issue with using Declare Indexes in an unexpected way: Declare Index works only when a property that is tracked is changed, and merging a branch rule to base ruleset does not change any tracked property. However, there was a Force Reindex happening when the saved instance had a different pzInskey than one that already existed in the db. This occurred when the rule was merged to new ruleset where the pzInskey in the DB would be null, and was expected behavior. In order to ensure Declare Indexes fire during a merge, pzReindex will be set to true in the Merge Wizard before saving the rule while doing branch merge. It will be reset/set to false after the rule has been merged and saved to avoid the additional overhead of triggering re-indexing every time the rule is saved afterwards. Further enhancements will be made in an upcoming release regarding parameter handling in templatised UIs.

SR-C68901 · Issue 411286

Multiple fixes made to handleXThreadChanges to resolve IE11 latency for opening cases/assignments

Resolved in Pega Version 8.2

After upgrade there was a performance issue with IE11 when opening a case from the search box or opening the assignments, and alerts were triggered from PDC indicating "ClientPageLoad has exceeded the elapsed time". This was caused by IE stopping the triggering of requests until a client processes was done, causing increased latency when compared to using Chrome. To resolve this, multiple fixes have been made to the handling for handleXThreadChanges in setTimeout.

SR-C65748 · Issue 411169

Multiple fixes made to handleXThreadChanges to resolve IE11 latency for opening cases/assignments

Resolved in Pega Version 8.2

After upgrade there was a performance issue with IE11 when opening a case from the search box or opening the assignments, and alerts were triggered from PDC indicating "ClientPageLoad has exceeded the elapsed time". This was caused by IE stopping the triggering of requests until a client processes was done, causing increased latency when compared to using Chrome. To resolve this, multiple fixes have been made to the handling for handleXThreadChanges in setTimeout.

SR-C79762 · Issue 419157

Decision table decision shape produces correct connector

Resolved in Pega Version 8.2

After adding a decision shape and making its type "Decision Table", the connector that was automatically built showed the condition type as "Result", but incorrectly labeled it as a When rule. This was traced to a missed use case in the decision related connectors, and has been corrected.

SR-C65417 · Issue 406207

Autocomplete control corrected for dynamic index section

Resolved in Pega Version 8.2

When section was defined on the static index of pagelist (i.e. pagelist(1) ), the value selected in autocomplete was being set properly but when section was defined on dynamic index of pagelist (i.e. pagelist() ), the value selected in autocomplete was not being set. This was traced to LAST and FIRST predicates not being correctly resolved in templating. To correct this, while rendering auto complete with pzpega_ui_template_autocomplete.js file, the system will resolve predicates using the currentContext.resolvePredicates API.

SR-C77107 · Issue 417088

Added check for sending email attachments with XML data

Resolved in Pega Version 8.2

When using SendEmailNotification to send an email with an attachment, the attachment was added but had no content when the email was received. In this case, if the property pyRemoveXML was true and if the email attachment content had XML data and did not contain a <pagedata tag, then the removeXML() method was returning "" as the email attachment content. This has been fixed by adding a check so if the property pyRemoveXML is true and if the email attachment content has XML data and doesn't contain the <pagedata tag, then it will return the original content itself.

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