SR-A99473 · Issue 266934
Documentation updated for Obj-Delete-By-Handle method
Resolved in Pega Version 7.2.2
The documentation for the Obj-Delete-By-Handle method has been updated to clarify that the Obj-Delete-By-Handle method will require the object to be locked if either the class or class group allows locking.
SR-A95291 · Issue 270315
Deprecated Access Groups documentation updated
Resolved in Pega Version 7.2.2
The documentation lead-in to the Deprecated Access Groups section has been updated for clarification: These access groups are retained after upgrades to support applications created in Version 4.2 and Version 5.X systems. They are deprecated and not recommended for continued use. These access groups appear only on systems that are upgraded from PRPC 6.x or earlier.
SR-A99855 · Issue 266703
Help file corrected for JSP tag
Resolved in Pega Version 7.2.2
The help for the JSP Tag "" is incorrect: It reads: example string of 'pyActivityName', but it should be 'pyActivity'. This has been fixed.
SR-A94342 · Issue 263882
Inserted missing word in property-set-html doc
Resolved in Pega Version 7.2.2
The missing word "is" has been added in In the doc article that comes up when the "?" is clicked while filling in the parameters for the property-set-html activity method, which previously read "Identify the property that to receive its value from stream processing".
SR-A76148 · Issue 251342
Documentation updated for running BIX from the command line
Resolved in Pega Version 7.2.2
When attempting to run BIX from the command line within a Linux environment, an error is thrown: Error: Could not find or load main class com.pega.pegarules.data.internal.access.ExtractImpl This was a local error in the setup of the bix.sh script, and the BIX documentation has been updated to clarify the requirements.
SR-A77514 · Issue 239717
@baseclass!pyMemo has been made available
Resolved in Pega Version 7.2.2
Opening up property pyMemo (which applies to Link-) and trying to save it into a custom ruleset generated an error due to @Baseclass having a final version of pyMemo. To correct this, @baseclass!pyMemo has been made available.
SR-B5634 · Issue 274715
Stack frame handling made more robust
Resolved in Pega Version 7.2.2
Stack frame handling has been made more robust to prevent the stack trace from getting out of sync in cases where the strategy execution throws an exception.
SR-A89757 · Issue 258099
SaveAs history carries previous version and ruleset info
Resolved in Pega Version 7.2.2
When saving as a rule from particular version, the rule history did not correctly carry over the information about the origin ruleset version (Previous version and ruleset) This was an error caused by recent changes to the WBSaveAs record management API, and has been fixed with new parameters added to "call SaveAs" on Rule-!WBSave into the record management API.
INC-202878 · Issue 713792
Handling updated for social messaging items with very large embedded images
Resolved in Pega Version 8.6.5
Job scheduler was running out of memory while handling large/multiple files, causing nodes to crash while handling Social Messaging items. Inline images were also not being sent in the ACK email. Investigation traced this to a custom job scheduler and activity used to create PDFs from email communication and send the PDFs to a third-party system. This used the standard Email Triage/PegaSocial functionality for the emails, which were stored as instances of PegaSocial-Message. The custom Job scheduler and activity then leveraged the Data Page D_pxEmailPosts to retrieve the emails in order to harvest the text from the emails. The issue occurred when a number of the emails had multiple or large embedded images in them, meaning the PegaSocial-Message instances are very large. This resulted in the node running out of memory and crashing. To resolve this, code has been added to support inline images in ACK email and the complete message from Pulse will be used instead of the original message as the email body for the ACK email.
INC-211974 · Issue 706616
UpgradeInteractionCase modified to update work page on save
Resolved in Pega Version 8.6.5
After update, service cases were failing to unpend when using a custom data transform that accessed the D_CorrespondenceCase data page. Investigation showed the D_CorrespondenceCase data page was internally using the D_pxGetInteractionCaseDetails data page; this call upgraded and saved and committed the case but this commit released the lock which the custom data transform had acquired. Because this happened before accessing the CorrespondenceCase datapage, it led to an error while committing the service case details. To resolve this, the postprocessing activity "pyUpgradeInteractionCase" of D_pxGetInteractionCaseDetails has been modified to write the update on the work page as soon as a save is performed.