SR-A102018 · Issue 270086
Creating REST integration works from JSON file
Resolved in Pega Version 7.2.2
Creating REST integration from JSON file was failing due to the same name attribute 'agent' in the JSON having different modes - page and string. Code to perform a rename in case of conflicts was already present, but in the given case (JSON file) properties were created in descending order but saved in ascending order and the error occurred. To resolve this issue, the conflicting properties will be renamed when created such that the order of creation does not affect the creation of the properties.
SR-A22374 · Issue 247987
File Listener waits for PRPC node usability
Resolved in Pega Version 7.2.2
During server start up, it was noticed that the file listener started processing files waiting in the target directory before the agent was instantiated. This caused an Null Pointer Error. The file listener has now been modified to process the files only if the PRPC node is usable.
SR-A69773 · Issue 249802
Failed SOAP OOM error corrected
Resolved in Pega Version 7.2.2
If a workflow included heavy use of Connect-SOAP operations and the back-end SOAP service was down, the extensive SOAP exceptions were leading to a JVM OOM error. This was due to the cleanupTransport not properly accounting for failed cases, and changes have been made to do an explicit cleanup in the catch block.
SR-A96437 · Issue 265628
Modified declare expression truncation for integration class
Resolved in Pega Version 7.2.2
If the name of the integration class picked by the wizard from the request XML exceeded 64 characters. an error appears. This is expected behavior. However, the error was persistent even after changing the class name, and the issue has been addressed by updating the truncation used by the pyAuthentication declare expression.
SR-A86781 · Issue 256593
Check added to ensure JMS agent starts before Listener begins processing
Resolved in Pega Version 7.2.2
If the the JMS Listener started before the agent during server startup, a Null Pointer Error was generated if there were items in the queue. This has been corrected by adding a check to ensure the agent is running before the Listener starts.
SR-A92387 · Issue 261229
Guardrail warning for offset/length removed from MapStructure rule
Resolved in Pega Version 7.2.2
In Map Structured rules, a guardrail warning was coming up for every row which had non-continuous length due to excess offset. This warning was generic without specifying the row number, and every time an attempt was made to justify the warning it was unrecognized and generated another warning. This left the rule with unjustified warnings on saving. As this rule is used often for generating excel sheets and formatting data neatly, it is not possible to provide the offset and length as expected by the Map Structured rule and there was a huge impact on the compliance score of applications when there was more than one Map Structured rule. As this is a common use case, the guardrail warning has been removed.
SR-A93912 · Issue 261494
SSLUtils modified to support app container keystore/truststore
Resolved in Pega Version 7.2.2
Keystore and truststore configured at application container level were not being used by SOAP Connectors. To facilitate use, when SSL settings are not provided at a rule level SSLUtils will create a wrapper around the Java default SSL artifact and use that.
SR-A93912 · Issue 264848
SSLUtils modified to support app container keystore/truststore
Resolved in Pega Version 7.2.2
Keystore and truststore configured at application container level were not being used by SOAP Connectors. To facilitate use, when SSL settings are not provided at a rule level SSLUtils will create a wrapper around the Java default SSL artifact and use that.
SR-A76847 · Issue 255143
Outbound Correspondence enhanced to handle Inline Content
Resolved in Pega Version 7.2.2
Pega's outbound email features previously only allowed for specifying "attachments" for inclusion for the email messages that are sent out from the Pega application and did not support "inline content". This led to all images in a Correspondence object being packaged as attachments when Pega sent Correspondence as email, and images might fail to appear in the body of outbound Correspondence when the recipient opens the message in their email client. Images intended to be part of the message body would appear as attachments to the email message. To enhance the mail services, a new PageList property "pyInlineContent" of type "Embed-EmailAttachment" has been added to the preexisting "Data-EmailAttachments" class. The "SendEmailMessage" Rule-Utility-Function has been enhanced to detect when the new "pyInlineContent" property is populated. If the email is HTML formatted, the content in the list will be given a disposition of "inline" and packaged with the HTML body in a message part of type "multipart/related" for proper consumption by email clients. If the email is not an HTML email, the "inline" content will NOT be branded as inline content, so that it appears as an attachment when the email message is opened. The "SendEmailNotification" in Pega-EventProcessing has been WITHDRAWN and replaced with a new version in SendEmailNotification which has an updated "prepare" step (#2) that puts the data for images in HTML (Corr) into the new "pyInlineContent" property of the Email Attachments page (if such a page exists), so that SendEmailMessage can process them correctly.
SR-A93295 · Issue 260100
Page-Copy given 'when' rule for assembler switch
Resolved in Pega Version 7.2.2
Performance issues relating to XML stream assembly were identified as an assembler switch problem in the Page-Copy Activity Method step. To improve response, a 'when' rule has been instituted to control switching between the old assembly Action aspect or the Model aspect in a scoped way, but can be overridden in the parse XML rule applies-to class.